[Libreoffice-bugs] [Bug 152335] Space effect changes when saving to PPTX.
https://bugs.documentfoundation.org/show_bug.cgi?id=152335 Tibor Nagy (NISZ) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |nagy.tib...@nisz.hu |desktop.org | Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90933] EDITING: Moving an image or object changes positions relative to settings
https://bugs.documentfoundation.org/show_bug.cgi?id=90933 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||6086 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136086] Selected image moves down to next page when pressing arrow up
https://bugs.documentfoundation.org/show_bug.cgi?id=136086 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=90 ||933 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152335] Space effect changes when saving to PPTX.
https://bugs.documentfoundation.org/show_bug.cgi?id=152335 --- Comment #2 from NISZ LibreOffice Team --- Created attachment 183935 --> https://bugs.documentfoundation.org/attachment.cgi?id=183935=edit Screenshot of the problem -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152335] Space effect changes when saving to PPTX.
https://bugs.documentfoundation.org/show_bug.cgi?id=152335 --- Comment #1 from NISZ LibreOffice Team --- Created attachment 183934 --> https://bugs.documentfoundation.org/attachment.cgi?id=183934=edit Sample file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152335] New: Space effect changes when saving to PPTX.
https://bugs.documentfoundation.org/show_bug.cgi?id=152335 Bug ID: 152335 Summary: Space effect changes when saving to PPTX. Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoff...@nisz.hu Description: When I create a shape in powerpoint and save it to pptx, then I open it in libreoffice and save it as a pptx the space effect changes on the shape. Steps to Reproduce: 1. open the attached file in Libreoffice after saving save as PPTX. 2. Open the file in Powerpoint. Actual Results: The space effect of the shape is changed. Expected Results: Space effect does not change the shape. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: bfe33d42a2381bce194cc6fe15b830902f7c8443 CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #18 from Heiko Tietze --- This example is again overly complex. Please define STR like: use PS "Text Body", change attribute X to Y, apply to paragraph. To repeat the conclusion, if no tab stop is defined it uses the indentation, which makes sense to me. You are free to challenge this and to suggest alternative. If you reopen, please add your expectation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126477] FILEOPEN DOCX Embedded OLE document does not show charts
https://bugs.documentfoundation.org/show_bug.cgi?id=126477 Tünde Tóth changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |tund...@gmail.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139232] Image refuses moving or jumps to unexpected position when attempting to move the image with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=139232 Dieter changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||6086 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Dieter changed: What|Removed |Added Depends on||136086 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136086 [Bug 136086] Selected image moves down to next page when pressing arrow up -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Dieter changed: What|Removed |Added Depends on||136086 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136086 [Bug 136086] Selected image moves down to next page when pressing arrow up -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136086] Selected image moves down to next page when pressing arrow up
https://bugs.documentfoundation.org/show_bug.cgi?id=136086 Dieter changed: What|Removed |Added Blocks||87740, 103152 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||9232 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87740 [Bug 87740] [META] Anchor and text wrapping bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136086] Selected image moves down to next page when pressing arrow up
https://bugs.documentfoundation.org/show_bug.cgi?id=136086 Dieter changed: What|Removed |Added Summary|Anchors interacting with|Selected image moves down |each other |to next page when pressing ||arrow up Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #11 from Dieter --- I confirm, that there is a problem, but it is different from what is described in original bug report. For example saving as docx and reloading doesn't sole the problem. So I would focus this report to the first problem described in comment 0 Steps: 1. Open attachment 164652 2. Select image on second page and press arrow up Actual result: Image jumps to second page Expected result: Image moves up Do you agree, Telesto? Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152332] [FILESAVE] tab delimited .txt and .tsv files are overwritten as comma delimited by default
https://bugs.documentfoundation.org/show_bug.cgi?id=152332 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Mike Kaganski --- What field separators are checked when you open the TSV? If you do not change the defaults, three of them (tab/comma/semicolon) are checked, and then application does not know which of those are actually expected in the file (the filter settings are stored with the opened document); when saved, it would use one of the selected separators, which happens to be the comma. Does this happen when you only check tab on import? (Tested that it works OK here using both 7.3.0.3 and 7.4.3.2, when tab is the only selected separator.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149155] Restore Down barely shrinks the window, doesn't use last known settings
https://bugs.documentfoundation.org/show_bug.cgi?id=149155 Dieter changed: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment #4 from Dieter --- It's not a question of understanding. But I simply couldn't reproduce. It seems, your've used an old version of LO. So please retest with actual version LO 7.4. And please also try with a clean usee profile as requested in comment 1. => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120479] Crash in: libc-2.27.so
https://bugs.documentfoundation.org/show_bug.cgi?id=120479 Dieter changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #28 from Dieter --- Bug was confirmed by bug reporter (see history). So status should be UNCONFIRMED (Jacques, you can't confirm your own bugs). But question from comment 27 is still valid. Jacques, can you still reproduce the bug with an actual version of LO? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139444] VLOOKUP function very slow on Large Tables in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=139444 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2334 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152334] New: Autofilter doesn't work on a custom array function range
https://bugs.documentfoundation.org/show_bug.cgi?id=152334 Bug ID: 152334 Summary: Autofilter doesn't work on a custom array function range Product: LibreOffice Version: 7.3.0.0 alpha0+ Hardware: All URL: https://ask.libreoffice.org/t/filtering-on-results-of- xpysort-in-calc/84731 OS: All Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com CC: er...@redhat.com, l.lu...@collabora.com Created attachment 183933 --> https://bugs.documentfoundation.org/attachment.cgi?id=183933=edit XPySort + autofilter 1. Install XPySort.oxt from https://forum.openoffice.org/en/forum/viewtopic.php?f=21=56916#p474771 2. Open the attachment (taken from https://ask.libreoffice.org/t/filtering-on-results-of-xpysort-in-calc/84731/3) 3. Using the autofilter on SortedData.R1, uncheck the item "No" In 7.3 and later versions, all the data gets filtered out, including the single 7th row that has the "Yes" value in column R. 7.2 and prior work OK, showing the row 7, as expected. This is a regression from commit ec0edb0969c23b25576f4d1b3b2ee5d3f21990ad (optimize VLOOKUP by returning SharedString if possible (tdf#139444), 08-10-2021). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150973] Use only SVG for the toolbar icons
https://bugs.documentfoundation.org/show_bug.cgi?id=150973 --- Comment #13 from Tomaz Vajngerl --- (In reply to Roman Kuznetsov from comment #12) > I remember that LO had some problems with the SVG->PNG icon converting. I > mean LibreOffice doesn't show the SVG icons directly, first it converts SVG > to PNG > > Tomaz, what do you think today about the suggestion? Is there today some > technical reason to have PNG icon themes and don't use only SVG for all > icons? I don't think anything changed. There are some bugs that need discovering and fixing in the SVG importer, drawinglayer, outputdevice, backend to get rendering sizes correctly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137326] Tight extensions report wrong rating and download numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=137326 Heiko Tietze changed: What|Removed |Added URL||https://redmine.documentfou ||ndation.org/issues/3631 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 --- Comment #68 from Olaf Guse --- I (In reply to Alex Thurgood from comment #67) > @Olaf : is the trace when it hangs the same, or different to the one I > identified in bug 151894? > > If the trace on hang is not the same as the one in bug 151894, it might be a > manifestation of bug 95191 or bug 98491. > > What I'm trying to say is that even if this bug report appears to be fixed, > the continued problem you are experiencing needs to be investigated again. > I'll reopen bug 151894 and set as unconfirmed pending further investigation. @Alex: For me there is no change in behavior with the new build. Maybe reopen 151894 and verify the bug 151894 with the new build by a other user would help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152333] Crash opening saved spreadsheet which was modified with macro
https://bugs.documentfoundation.org/show_bug.cgi?id=152333 --- Comment #3 from Jim Avera --- Is the crash dialog supposed to display a "crash signature"? It did not seem to show anything specific. The second "Crash Report" window only shows this: <> --- Also: The crash only occurs the *first* time LO is started after the spreadsheet is saved. After clicking through the crash dialog and exiting LO, a subsequent start does not cause a crash. It is necessary to click the yellow "Reload csv" button and do Save + Exit, then start again to see another crash. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152333] Crash opening saved spreadsheet which was modified with macro
https://bugs.documentfoundation.org/show_bug.cgi?id=152333 --- Comment #2 from Jim Avera --- Created attachment 183932 --> https://bugs.documentfoundation.org/attachment.cgi?id=183932=edit tickers.csv data file which MUST be in /tmp to reproduce the bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152333] Crash opening saved spreadsheet which was modified with macro
https://bugs.documentfoundation.org/show_bug.cgi?id=152333 --- Comment #1 from Jim Avera --- Created attachment 183931 --> https://bugs.documentfoundation.org/attachment.cgi?id=183931=edit Spredsheet needed to reproduce bug (t.ods) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152333] New: Crash opening saved spreadsheet which was modified with macro
https://bugs.documentfoundation.org/show_bug.cgi?id=152333 Bug ID: 152333 Summary: Crash opening saved spreadsheet which was modified with macro Product: LibreOffice Version: 7.5.0.0 alpha0+ Master Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com Description: A specific sequence of operations results in a Crash dialog when LO is started again after saving a spreadsheet and exiting. The problem seems to depend on the details of how the spreadsheet was modified before it was saved (the modification happens in Basic macros which delete and re-create a sheet). No crash report opens after I click "Send Crash Report". This might be a problem where LO can not make my browser open the crash report page. While I am using a non-standard browser (firefox-esr) I think I have configured my desktop system to use it correctly: The command "xdg-open " works. FWIW I'm running xubuntu 22.04.1 LTS; the desktop uses xfce, not gnome. STEPS TO REPRODUCE: 1. Download both the "t.ods" and "tickers.csv" files and place them in the /tmp directory (tickers.csv *must* be in /tmp -- the test macro is hard-coded to look for /tmp/*.csv) Note: Macro security should be set to "Medium" (prompt each time). 2. /path/to/lo t.ods Enable macros when prompted. 3. Click the yellow "Reload csv" button (the tickers.csv file *must* be in /tmp and no other .csv files in /tmp) 4. File->Save 5. File->Exit 6. /path/to/lo t.ods (crash dialog appears) Note: After clicking through the crash dialogs the spreadsheet opens anyway, so this is odd. Steps to Reproduce: . Actual Results: . Expected Results: . Reproducible: Always User Profile Reset: Yes Additional Info: I did delete $HOME/.config/libreoffice/r/user which is supposed to have profile data (the 'util' directory never re-appeared, so I suspect dev builds store profile somewhere else). I also entered "safe" mode and did "reset to defaults". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137203] Conditional Formats corrupted by save/exit/reload
https://bugs.documentfoundation.org/show_bug.cgi?id=137203 Jim Avera changed: What|Removed |Added Resolution|INSUFFICIENTDATA|WORKSFORME --- Comment #15 from Jim Avera --- With latest master the corrupted Conditional Formats no longer occur, but a crash occurs every time when starting LO the second time in the test sequence, i.e. after running the macros and doing a save and exit. Since this looks like a different bug, I'm going to close this as WORKSFORME and open a new bug for that crash. -Jim Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 98d8adc5b377039d5dee0d5046ece721010a960c CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137203] Conditional Formats corrupted by save/exit/reload
https://bugs.documentfoundation.org/show_bug.cgi?id=137203 Jim Avera changed: What|Removed |Added Attachment #183930|Updated test file t.ods |Updated test file t.ods description|(fixes comment #15)(See |(fixes comment #10)(See |Steps to Reproduce &|Steps to Reproduce & |Comment #12)|Comment after #14) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137203] Conditional Formats corrupted by save/exit/reload
https://bugs.documentfoundation.org/show_bug.cgi?id=137203 Jim Avera changed: What|Removed |Added Attachment #183930|Updated test file t.ods |Updated test file t.ods description|(fixes comment #10)(See |(fixes comment #15)(See |Steps to Reproduce &|Steps to Reproduce & |Comment #12)|Comment #12) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137203] Conditional Formats corrupted by save/exit/reload
https://bugs.documentfoundation.org/show_bug.cgi?id=137203 Jim Avera changed: What|Removed |Added Attachment #176574|0 |1 is obsolete|| --- Comment #14 from Jim Avera --- Created attachment 183930 --> https://bugs.documentfoundation.org/attachment.cgi?id=183930=edit Updated test file t.ods (fixes comment #10)(See Steps to Reproduce & Comment #12) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152330] Calc: cannot print darkened gridlines and there is no way to widen them at all
https://bugs.documentfoundation.org/show_bug.cgi?id=152330 --- Comment #2 from e...@mailfence.org --- Phew. That did work if I first selected the area, then clicked the tab, then printed. The strange thing is that even though there was only 1 sheet and 1 page shown, it printed Page 1,2,3, though that is easy enough to control. Thanks for your help, V Stuart. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V6.1 (same sheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 wzpd...@gmail.com changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147565] Browsing comments in the navigation pane also browses hidden solved comments
https://bugs.documentfoundation.org/show_bug.cgi?id=147565 --- Comment #15 from annagrimes --- Drift Hunters is a one-of-a-kind game in which you can design your own car. https://drift-hunters.io -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V6.1 (same sheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 --- Comment #10 from wzpd...@gmail.com --- Yes aware Customize can be accessed via Tools/Customize. Same code and error is at close though. Would note running Win 11 not 10 so may be difference there. Have tried Safe mode with this system with same result. Might take a while but I will try 7.4.3 to see if I can reproduce via any of the three paths mentioned including Safe mode. Will report results. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152047] Graphics disappear when document moved in another folder
https://bugs.documentfoundation.org/show_bug.cgi?id=152047 --- Comment #10 from software.v9...@slmail.me --- I cannot believe that: 10 years discussions about inserting relative links? The first thread goes back to 2012 So we have a link jubilee!! As far as I've skimmed the topic, I did not find a single reason why inserting absolute and relative links shouldn't work on document level -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152330] Calc: cannot print darkened gridlines and there is no way to widen them at all
https://bugs.documentfoundation.org/show_bug.cgi?id=152330 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152330] Calc: cannot print darkened gridlines and there is no way to widen them at all
https://bugs.documentfoundation.org/show_bug.cgi?id=152330 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Created attachment 183929 --> https://bugs.documentfoundation.org/attachment.cgi?id=183929=edit Calc sheet with cell Border applied for print/export Wait! Some reason you do not apply Borders from the 'Format Cells...' dialog? >From the 'Borders' tab, select the "Outer Border and All Inner Lines" preset. You can then select the Line 'Width' Select the entire sheet, or just portion of a sheet with cell data to format. Those "gridlines" certainly do print! =-testing-= Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 958c08ad86d56839faf28a02097500bad7b1eb76 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151062] The UI flickering and lagging in GTK3. The Page following scroll from style format when it scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=151062 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149063] Writer "hanging" regularly whilst amending documents
https://bugs.documentfoundation.org/show_bug.cgi?id=149063 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149063] Writer "hanging" regularly whilst amending documents
https://bugs.documentfoundation.org/show_bug.cgi?id=149063 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148912] "Rename Slide" does not persist when saving and reopening slide deck
https://bugs.documentfoundation.org/show_bug.cgi?id=148912 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148912] "Rename Slide" does not persist when saving and reopening slide deck
https://bugs.documentfoundation.org/show_bug.cgi?id=148912 --- Comment #3 from QA Administrators --- Dear Noloader, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148905] Crash when copying text from text box in document to header in same document
https://bugs.documentfoundation.org/show_bug.cgi?id=148905 --- Comment #3 from QA Administrators --- Dear Peter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148905] Crash when copying text from text box in document to header in same document
https://bugs.documentfoundation.org/show_bug.cgi?id=148905 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149445] LibreOffice prints garbage
https://bugs.documentfoundation.org/show_bug.cgi?id=149445 --- Comment #5 from QA Administrators --- Dear Han Leushuis, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149442] Right Click Open Hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=149442 --- Comment #2 from QA Administrators --- Dear Nick, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59587] undefined: impress doesn't refresh screen after spyral animation
https://bugs.documentfoundation.org/show_bug.cgi?id=59587 --- Comment #6 from QA Administrators --- Dear paolo_debortoli, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138426] Right arrow causes a large unexpected column jump ( part 2 )
https://bugs.documentfoundation.org/show_bug.cgi?id=138426 --- Comment #6 from QA Administrators --- Dear Xisco Faulí, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137326] Tight extensions report wrong rating and download numbers
https://bugs.documentfoundation.org/show_bug.cgi?id=137326 --- Comment #2 from QA Administrators --- Dear Heiko Tietze, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134701] Zooming in/out in single page view slowish
https://bugs.documentfoundation.org/show_bug.cgi?id=134701 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133789] BASIC function DIR does not deliver correct result list
https://bugs.documentfoundation.org/show_bug.cgi?id=133789 --- Comment #17 from QA Administrators --- Dear joachim, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128022] Triple table border from DOC/DOCX not recognized by Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=128022 --- Comment #2 from QA Administrators --- Dear Timur, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125150] Table of Contents disappears if empty when saving as docx
https://bugs.documentfoundation.org/show_bug.cgi?id=125150 --- Comment #4 from QA Administrators --- Dear arrowdodger, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120479] Crash in: libc-2.27.so
https://bugs.documentfoundation.org/show_bug.cgi?id=120479 --- Comment #27 from QA Administrators --- Dear Jacques Beckand, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119032] FILEOPEN DOCX Word paragraph borders imported incorrectly (with 24 border styles)
https://bugs.documentfoundation.org/show_bug.cgi?id=119032 --- Comment #7 from QA Administrators --- Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152332] [FILESAVE] tab delimited .txt and .tsv files are overwritten as comma delimited by default
https://bugs.documentfoundation.org/show_bug.cgi?id=152332 James Leader changed: What|Removed |Added Hardware|All |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152332] [FILESAVE] tab delimited .txt and .tsv files are overwritten as comma delimited by default
https://bugs.documentfoundation.org/show_bug.cgi?id=152332 James Leader changed: What|Removed |Added Summary|tab delimited .txt and .tsv |[FILESAVE] tab delimited |files are overwritten as|.txt and .tsv files are |comma delimited by default |overwritten as comma ||delimited by default -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152332] New: tab delimited .txt and .tsv files are overwritten as comma delimited by default
https://bugs.documentfoundation.org/show_bug.cgi?id=152332 Bug ID: 152332 Summary: tab delimited .txt and .tsv files are overwritten as comma delimited by default Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: james@gmail.com Description: Opening a tsv file (.tsv or .txt) that is tab delimited and then clicking save will erase the formatting of the file and overwrite as a comma delimited file by default. A quick google shows this issue has been present in 2015 https://ask.libreoffice.org/t/calc-saving-my-tsv-file-as-a-csv-without-asking/19709 There is a work around: needing to use additional clicks to save as a .csv with "edit filter settings" checked, then selecting field delimiter: "tab", and finally renaming the file to the original file extension. https://ask.libreoffice.org/t/how-to-generate-calc-tab-delimited-output/14591 Following this procedure to export the file correctly once seems to solve the issue for subsequent saves of all files. Steps to Reproduce: 1. Fresh install of Linux Mint 21.0 2. Open a .txt file that is tab delimited 3. Click the save icon 4. Re-open the file in a text editor to show that the formatting has been changed to comma delimited 5. Reproducible until "save as" with filter 1 time Actual Results: Formatting was changed from tab to comma delimited (file extension still .txt) Expected Results: Formatting should be preserved as tab delimited Reproducible: Always User Profile Reset: No Additional Info: Once doing an export with filter set to tab delimited once, the issue appears to be solved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152331] LibreOffice Base - Autovalues not showing in report
https://bugs.documentfoundation.org/show_bug.cgi?id=152331 --- Comment #1 from ro...@outlook.com --- Created attachment 183928 --> https://bugs.documentfoundation.org/attachment.cgi?id=183928=edit Pictures of the problem I really appreciate your help in fixing this. I'm not a developer nor a programmer, I just want to set up data bases to make my work easier. You, guys, do an incredible job with LibreOffice. I don't need to know all the steps you take to test and try, chances are I'm not going to understand a word. Just let me know if it was possible to fix the bug or when it's fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152331] New: LibreOffice Base - Autovalues not showing in report
https://bugs.documentfoundation.org/show_bug.cgi?id=152331 Bug ID: 152331 Summary: LibreOffice Base - Autovalues not showing in report Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ro...@outlook.com Description: I'm using this version Libreoffice base 7.4.3.2(x64) on Windows 11 on a PC. I have setup a small base with the idea to create invoices with a customer table, invoice table and task table. I used the invoicing tamplate available in Base by using the wizard. I have set the auto value for the invoice numbers starting at 0. Then I have created a form to write the invoice and a report for print which involves queries, everything works fine untill I run a report where I use the field InvoiceID (autovalue) The field with autovalues doesn't appear in the report. The label is there but the Data Field shows as blank space. I can't find the solution and I'm totally new to DBases and have no clue about SQL. On top of that, the report builder keeps crashing LibreOffice and its window behaves weirdly. I have to hit windows+arrow up and down several times so the windows stabilize and let me edit. Sometimes it works other times it crashes. Steps to Reproduce: 1. Create tables with primary key as auto value, in my case, InvoiceID, CustomerID and TaskID 2. Add the primary keys to a query 3. Create a report that includes the auto values Actual Results: In the final document, I should be able to see a fat round zero besides the labels Invoice no., Customer no. and Task nobut nothing. The other values from the query show perfectly. I ran another report with CustomerID and TaskID auto value and its the same problem. it seems it's only autovalues that don't show. Besides, it looks like the autonumber is not counting. I entered data for two different invoices for the same customer, invoices no. 0 and no. 1, for $ 75 each, but instead of doing two different documents, it puts everything together in the same final document created on Write showing a total of $ 150. Expected Results: Just for it to work as a normal invoice data base. Reproducible: Always User Profile Reset: No Additional Info: You can see pictures in here https://ask.libreoffice.org/t/libreoffice-base-id-auto-increment-problem-printing-reports/52219/5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152330] New: Calc: cannot print darkened gridlines and there is no way to widen them at all
https://bugs.documentfoundation.org/show_bug.cgi?id=152330 Bug ID: 152330 Summary: Calc: cannot print darkened gridlines and there is no way to widen them at all Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: g...@pm.me Description: This has been maddening for years and has caused me to have to use other programs. Gridlines print very faintly, almost not visible. There is no way to darken them. And as far I can tell, there is not even a way to make them wider, only change their color on the screen, which does not change how they print at all. This seems like a really simple fix. I hope it is, and I hope it will get fixed pronto! Steps to Reproduce: 1. Duh, print a spreadsheet and notice how faint the gridlines are, then discover there is no way to change that. 2.Attempt to widen the gridlines, and discover there is no way to do that either. 3.Feel frustrated. Actual Results: See above. Expected Results: See above. Reproducible: Always User Profile Reset: No Additional Info: See above. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152134] assign user macro to Tools menu fails on V7.4.2.3.x64 (Windows11) works on Windows8.1 V6.1 (same sheet)
https://bugs.documentfoundation.org/show_bug.cgi?id=152134 --- Comment #9 from Stéphane Guillou (stragu) --- I could not reproduce the issue with: Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: threaded nor: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (en_AU.UTF-8); UI: en-US Calc: threaded Do you know that you can access the Customize menu directly from "Tools > Customize"? Do you also have the same issue when adding the macro to the menu using "Tools > Customize directly"? Please also try: - Installing version 7.4.3, and see if issue persists - See if you still see the issue in Safe Mode (Help > Restart in Safe Mode) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111957] Change the way to define relative vs absolute URLs
https://bugs.documentfoundation.org/show_bug.cgi?id=111957 Stéphane Guillou (stragu) changed: What|Removed |Added CC||software.v9...@slmail.me --- Comment #7 from Stéphane Guillou (stragu) --- *** Bug 152047 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152047] Graphics disappear when document moved in another folder
https://bugs.documentfoundation.org/show_bug.cgi?id=152047 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #9 from Stéphane Guillou (stragu) --- I marked this bug report as "solved - not a bug" because that is the language we have to use on this platform to categorise a report that describes a behaviour that works as intended. You are right, the issue you describe in your last comments is not yet solved. It is however already discussed in other, older bug reports. I mentioned bug 128216, which is about clarifying the display of relative links, but there is also an enhancement request that (if a developer decides to work on it) should make the situation better: bug 111957. Happy to mark your report as a duplicate of the enhancement request instead. Please feel free to participate in the conversation there. *** This bug has been marked as a duplicate of bug 111957 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150657] CALC Chart elements disappear when the data columns are hidden
https://bugs.documentfoundation.org/show_bug.cgi?id=150657 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #11 from Stéphane Guillou (stragu) --- Unfortunately, I still can't reproduce. Could you please see if the issue remains in version 7.4.3? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152328] Shift-F5 doesn't work & document doesn't open at last edit point
https://bugs.documentfoundation.org/show_bug.cgi?id=152328 Eyal Rozenberg changed: What|Removed |Added Summary|This happens in both|Shift-F5 doesn't work & |Windows and Ubuntu. Shift |document doesn't open at |F5 does not work. Also |last edit point |document always opens at| |page 1 not at last edit | |point. I do have personal | |info filled out.| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112286] [META] gtk3 themeing
https://bugs.documentfoundation.org/show_bug.cgi?id=112286 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152329 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152329 [Bug 152329] GTK3: Caption preview font is black when using OS dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=143344 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152329 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152329 [Bug 152329] GTK3: Caption preview font is black when using OS dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114426] [META] Caption bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114426 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152329 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152329 [Bug 152329] GTK3: Caption preview font is black when using OS dark mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152329] New: GTK3: Caption preview font is black when using OS dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=152329 Bug ID: 152329 Summary: GTK3: Caption preview font is black when using OS dark mode Product: LibreOffice Version: 6.3.6.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: low Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org Blocks: 112286, 114426, 143344 Created attachment 183927 --> https://bugs.documentfoundation.org/attachment.cgi?id=183927=edit screenshot of issue in LO 7.5 Steps: 0. Turn GNOME dark mode on 1. Open Writer 2. Insert a picture 3. Right-click > Insert Caption Actual results: Preview is in black on dark grey background, lacking contrast and looking out of place when other font is lighter throughout the UI. Versions: Version: 6.3.6.2 Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded all the way to a build from today: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 01a3cc1e55034f7703219d4bbb209de7c37bf07b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Not reproducible with KF5 VCL (cairo+xcb) nor on Windows. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112286 [Bug 112286] [META] gtk3 themeing https://bugs.documentfoundation.org/show_bug.cgi?id=114426 [Bug 114426] [META] Caption bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=143344 [Bug 143344] [META] Linux Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141586] Restoring last document position is unreliable
https://bugs.documentfoundation.org/show_bug.cgi?id=141586 Buovjaga changed: What|Removed |Added CC||stuco...@yahoo.com --- Comment #12 from Buovjaga --- *** Bug 152328 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152328] This happens in both Windows and Ubuntu. Shift F5 does not work. Also document always opens at page 1 not at last edit point. I do have personal info filled out.
https://bugs.documentfoundation.org/show_bug.cgi?id=152328 Buovjaga changed: What|Removed |Added Resolution|--- |DUPLICATE CC||ilmari.lauhakangas@libreoff ||ice.org OS|Windows (All) |All Status|UNCONFIRMED |RESOLVED --- Comment #1 from Buovjaga --- *** This bug has been marked as a duplicate of bug 141586 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152328] New: This happens in both Windows and Ubuntu. Shift F5 does not work. Also document always opens at page 1 not at last edit point. I do have personal info filled out.
https://bugs.documentfoundation.org/show_bug.cgi?id=152328 Bug ID: 152328 Summary: This happens in both Windows and Ubuntu. Shift F5 does not work. Also document always opens at page 1 not at last edit point. I do have personal info filled out. Product: LibreOffice Version: 7.3.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stuco...@yahoo.com This has been a problem with every version above 7.2.7.2. I have tried all versions through 7.4.3. Shift F5 does not work when in an open long document. Also document always opens at page 1 instead of point of last edit. I do have personal info filled out and versions prior to these work fine (using 7.2.7.2 until this bug is fixed). Happens on all 3 of my computers, all running Win10 with all the latest updates and my notebook running dual boot happens in both Windows and Ubuntu. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152326] wrong month sort in pivot table
https://bugs.documentfoundation.org/show_bug.cgi?id=152326 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|LibreOffice Calc|wrong month sort in pivot ||table -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152326] LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152326 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Hi John Could you please: - provide a document to test the issue - paste here the info copied from Help > About LibreOffice Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151996] crash when clicking autofilter (macOS 13)
https://bugs.documentfoundation.org/show_bug.cgi?id=151996 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||133092 Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #9 from Stéphane Guillou (stragu) --- Hi again Christopher You should now be able to see aarch64 builds: https://dev-builds.libreoffice.org/daily/master/current.html Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||151996 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151996 [Bug 151996] crash when clicking autofilter (macOS 13) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #17 from tor...@yahoo.com --- (In reply to Heiko Tietze from comment #15) ● ‘It happens only if no particular tab stop is defined.’ False; it happens also if a particular tab stop is defined beyond the indent. ● ‘It is very convenient for beginners to "indent per tab"’ Why would a beginner (or you) expect the cursor to obey an indent that does not even apply to the current line, where the FirstLineIndent is negative? In tabBal.odt, the 1st TabKey hit gives a ‘normal’ tab, because the cursor stops at the indent; only the 2nd TabKey hit gives the underlined tab; but this underlined tab begins at the indent, not at the margin, where the line begins. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151062] The UI flickering and lagging in GTK3. The Page following scroll from style format when it scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=151062 --- Comment #2 from Adam Lanman --- I am experiencing this same issue, most notably in Impress. I'm running 7.4.2.3 but have seen this consistently in previous versions. Sidebar menus (on the right, Properties, Styles, Gallery etc.) will flicker when I move my mouse cursor on the screen. Similar issues I've seen elsewhere suggest that this is a GTK-3 problem, and recommend disabling hardware acceleration and disabling background cache options. Neither suggestion led to any improvement. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.4.2~rc3-0ubuntu0.20.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152327] New: "Select unprotected cells" when no cells are unprotected makes data entry impossible
https://bugs.documentfoundation.org/show_bug.cgi?id=152327 Bug ID: 152327 Summary: "Select unprotected cells" when no cells are unprotected makes data entry impossible Product: LibreOffice Version: 6.3.6.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: major Priority: high Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org Blocks: 107450, 109139 Steps: 1. Open Calc 2. Edit > Select > Select unprotected cells (nothing is selected, as expected, given that all cells a protected by default) 3. Enter any data in a cell 4. Click out or press Enter Actual results: Data entered in cells instantly disappears. This issue does not happen when one or more cells are unprotected (with Edit > Cell protection). Workarounds: - Saving and reloading the document does restore the ability to add data to cells. - Selecting a cell range before entering data fixes the issue. Versions: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded A master build from today: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 01a3cc1e55034f7703219d4bbb209de7c37bf07b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Already in: Version: 6.3.6.2 Build ID: 2196df99b074d8a661f4036fca8fa0cbfa33a497 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107450 [Bug 107450] [META] Cell and sheet protection bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=109139 [Bug 109139] [META] Cell selection bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109139] [META] Cell selection bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109139 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152327 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152327 [Bug 152327] "Select unprotected cells" when no cells are unprotected makes data entry impossible -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107450] [META] Cell and sheet protection bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107450 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152327 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152327 [Bug 152327] "Select unprotected cells" when no cells are unprotected makes data entry impossible -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150848] Tab key should ignore indent
https://bugs.documentfoundation.org/show_bug.cgi?id=150848 --- Comment #16 from tor...@yahoo.com --- Created attachment 183926 --> https://bugs.documentfoundation.org/attachment.cgi?id=183926=edit file with indent and tabStop -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137879] LO should know not to try and recover temporary files
https://bugs.documentfoundation.org/show_bug.cgi?id=137879 --- Comment #10 from Eyal Rozenberg --- Seeing this with : Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 4; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Debian package version: 1:7.4.2-4 Note that, on Linux you can figure out which file is being used by opening a command-line and running `ps aux | grep soffice`. I found my Writer using /tmp/pid-/the_file_name as the filename, where is some number. This may depend on your choice of distribution though or the LO version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152078] Add control to Basic IDE to easily adjust the UI font size
https://bugs.documentfoundation.org/show_bug.cgi?id=152078 --- Comment #6 from Rafael Lima --- Created attachment 183925 --> https://bugs.documentfoundation.org/attachment.cgi?id=183925=edit Video showing the Zoom slider in action The zoom slider is now working as intended. See the attached video to see how it works. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 148945, which changed state. Bug 148945 Summary: LibreOffice crashes after un join Object Catalog and check on Lock Toolbars https://bugs.documentfoundation.org/show_bug.cgi?id=148945 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148945] LibreOffice crashes after un join Object Catalog and check on Lock Toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=148945 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE OS|Linux (All) |All Status|NEW |RESOLVED --- Comment #3 from Stéphane Guillou (stragu) --- Reproducible in: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded But not reproducible in: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 01a3cc1e55034f7703219d4bbb209de7c37bf07b CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I am confident this is the same issue as Bug 152154, which is fixed in master and will be in 7.4.4 Closing as duplicate. *** This bug has been marked as a duplicate of bug 152154 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152316] FILTER: "Show/Hide only the current item" when filtering in Calc is broken with the default focus
https://bugs.documentfoundation.org/show_bug.cgi?id=152316 --- Comment #6 from Kamil Páral --- OK, I also tested the latest nightly: Version: 7.5.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 98d8adc5b377039d5dee0d5046ece721010a960c CPU threads: 12; OS: Linux 6.0; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Both LO 7.4.3.2 and LO 7.5.0.0.alpha1+ are affected on my Fedora 37. LO 7.4.3.2, as mentioned, toggles all items on/off. LO 7.5.0.0.alpha1+ doesn't do anything, those filter buttons simply have no effect on the checkboxes in the item list. Only after manual selection it starts work properly, same as in LO 7.4.3.2. However, using SAL_USE_VCLPLUGIN=gen fixes both versions. It looks terrible (Windows 95-style), but those filter buttons work as expected right out of the box. So, this is likely a gtk3-related issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152154 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152154 [Bug 152154] Crash in libmergedlo.so when Object Catalog undocked and BASIC IDE closed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124891] [META] Basic IDE bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=124891 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152154 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152154 [Bug 152154] Crash in libmergedlo.so when Object Catalog undocked and BASIC IDE closed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104597] RTL script text runs are reversed on PDF import, PDFIProcessor::mirrorString misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=104597 --- Comment #111 from Commit Notification --- Kevin Suo committed a patch related to this issue. It has been pushed to "libreoffice-7-4": https://git.libreoffice.org/core/commit/0a19375b73b12885f9022d82cb51e9c268cc0d6a tdf#104597 related: restore the mirroring of Bidi_Mirrored characters It will be available in 7.4.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151363] [MacOS Apple Silicon] Writer+Calc hang frequently
https://bugs.documentfoundation.org/show_bug.cgi?id=151363 --- Comment #12 from Alex Thurgood --- (In reply to Christopher M. Penalver from comment #11) > Created attachment 183924 [details] > App Hung and Apple Crash Reporter caught it > > Version: 7.4.3.2 / LibreOffice Community > Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 > CPU threads: 8; OS: Mac OS X 13.0; UI render: default; VCL: osx > Locale: en-US (en_US.UTF-8); UI: en-US > Calc: threaded > Please try with a daily 7.5 dev build, where the problem is reported as having been fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152326] New: LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=152326 Bug ID: 152326 Summary: LibreOffice Calc Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hopkinsj...@gmail.com Description: LibreOffice Pivot table does not sort correctly the months. I went into customer sort and May has "May" around it the other months do not. When i sort by numeric date it works fine. It could be that the customer sort does not work because all of the other months are listed without quotation marks and the file cannot be seen as text. Actual Results: Go into pivot table with dates like a check register sort by months comes up as April Expected Results: I wanted the months to be consecutive Jan-November it went April through November Reproducible: Always User Profile Reset: No Additional Info: Should have arranged the months chronologically -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121378] Writer/UI: Adding Captions to Images is very Unpractical (Width of Image Changes with Width of Frame, Does not use Default Frame Style etc)
https://bugs.documentfoundation.org/show_bug.cgi?id=121378 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||7770 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32485] Settings on the image frame style lost when caption is applied
https://bugs.documentfoundation.org/show_bug.cgi?id=32485 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||7770 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147770] CAPTION: Empty space beween caption border and image (in specific document)
https://bugs.documentfoundation.org/show_bug.cgi?id=147770 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||1378, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=32 ||485 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121378] Writer/UI: Adding Captions to Images is very Unpractical (Width of Image Changes with Width of Frame, Does not use Default Frame Style etc)
https://bugs.documentfoundation.org/show_bug.cgi?id=121378 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=32 ||485 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32485] Settings on the image frame style lost when caption is applied
https://bugs.documentfoundation.org/show_bug.cgi?id=32485 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||1378 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147770] CAPTION: Empty space beween caption border and image (in specific document)
https://bugs.documentfoundation.org/show_bug.cgi?id=147770 Stéphane Guillou (stragu) changed: What|Removed |Added CC||j...@psilosoph.de --- Comment #7 from Stéphane Guillou (stragu) --- *** Bug 152302 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152302] Applying 'Insert Caption' to an image wrongly changes the relation for the vertical position
https://bugs.documentfoundation.org/show_bug.cgi?id=152302
--- Comment #7 from Stéphane Guillou (stragu)
---
Thank you Wolfgang and Heiko.
As I understand it, the spacing issue above the captioned image is an annoying
problem that could be fixed independently from the wider-ranging issue
described in bug 32485 ("should properties even be modified / transfered at
all?").
I would however close this bug as a duplicate of the existing Bug 147770, as it
covers the issue of the space above the image.
*** This bug has been marked as a duplicate of bug 147770 ***
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118017] [META] macOS Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=118017 Bug 118017 depends on bug 152317, which changed state. Bug 152317 Summary: macOS: Dark Mode: Calc: Highlighted sheet name unreadable https://bugs.documentfoundation.org/show_bug.cgi?id=152317 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
