[Libreoffice-bugs] [Bug 146678] New: This is first post
https://bugs.documentfoundation.org/show_bug.cgi?id=146678 Bug ID: 146678 Summary: This is first post Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Web Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: futureprofilez...@gmail.com Description: https://bugs.documentfoundation.org/ Actual Results: Not bug Expected Results: Not bug Reproducible: Always User Profile Reset: No Additional Info: Not bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125093] Windows: Honor "Zone.Identifier" stream, and open files from restricted zones in read-only mode
https://bugs.documentfoundation.org/show_bug.cgi?id=125093 --- Comment #3 from Stephan Bergmann --- (In reply to Mike Kaganski from comment #2) > Stephan: what do you think? Sounds like a plan, but I don't think I have any useful input. (Whenever I tried to modify the relevant sfx2 code, it looked like a complete mess to me. And instead of doing the alternate file stream access via UCB, it might also be plausible to do it directly via whatever Windows-only API in sfx2.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146677] which kind of error solved by QuickBooks diagnostic tool?
https://bugs.documentfoundation.org/show_bug.cgi?id=146677 Lily Acer changed: What|Removed |Added URL|https://cfi-blog.org/quickb | |ooks-connection-diagnostic- | |tool-download-install-and-u | |se/ | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146677] which kind of error solved by QuickBooks diagnostic tool?
https://bugs.documentfoundation.org/show_bug.cgi?id=146677 Lily Acer changed: What|Removed |Added URL||https://cfi-blog.org/quickb ||ooks-connection-diagnostic- ||tool-download-install-and-u ||se/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146677] New: which kind of error solved by QuickBooks diagnostic tool?
https://bugs.documentfoundation.org/show_bug.cgi?id=146677 Bug ID: 146677 Summary: which kind of error solved by QuickBooks diagnostic tool? Product: Impress Remote Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: acerlily1...@gmail.com Description: This kind of QuickBooks issue fixed by QuickBooks diagnostic tool update error 1207 update error 15270 update error 15223 update error 1328 Actual Results: it resolve due to QuickBooks diagnostic tool Expected Results: solved Reproducible: Always User Profile Reset: No Additional Info: https://cfi-blog.org/quickbooks-connection-diagnostic-tool-download-install-and-use/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146676] New: which kind of error solved by QuickBooks diagnostic tool?
https://bugs.documentfoundation.org/show_bug.cgi?id=146676 Bug ID: 146676 Summary: which kind of error solved by QuickBooks diagnostic tool? Product: Impress Remote Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: acerlily1...@gmail.com Description: This kind of QuickBooks issue fixed by https://cfi-blog.org/quickbooks-connection-diagnostic-tool-download-install-and-use/;>QuickBooks diagnostic tool update error 1207 update error 15270 update error 15223 update error 1328 Actual Results: its resolve by launching QuickBooks diagnostic tools Expected Results: problem solved Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: https://cfi-blog.org/quickbooks-connection-diagnostic-tool-download-install-and-use/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141652] FILESAVE: DOCX: Image distorted after RT
https://bugs.documentfoundation.org/show_bug.cgi?id=141652 --- Comment #3 from Justin L --- Xisco backported the fix to 7.1. Not sure exactly which point release it was, but the time was Mar 10, 2021 10:14. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146675] New: Users can't select "Reset", "Cancel", and "OK" if he/she is trying to Customize LO. Resolution Problem!
https://bugs.documentfoundation.org/show_bug.cgi?id=146675 Bug ID: 146675 Summary: Users can't select "Reset", "Cancel", and "OK" if he/she is trying to Customize LO. Resolution Problem! Product: LibreOffice Version: 7.2.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: prabesh...@gmail.com Created attachment 177422 --> https://bugs.documentfoundation.org/attachment.cgi?id=177422=edit Screencast video where user is trying to see hidden option I have experienced this issue since Ubuntu 19.04, 19.10, 20.04, Fedora 34 and now in Fedora 35. I tried to report in Ubuntu Launchpad and I did as you can see: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1889051 But it didn't receive any attention. Hardware: Dell Inc. Inspiron 5548 Processor: Intel® Core™ i5-5200U CPU @ 2.20GHz × 4 Graphics: Mesa Intel® HD Graphics 5500 (BDW GT2) Windowing System: Wayland OS-Type: 64-bit Kernel: Linux 5.15.12-200.fc35.x86_64 Resolution: 1366 x 768 (16:9) Desktop Enviroment: GNOME 41.2 I have also attached a new screencast down below to show what's happening. Q. How much reproducable? -> Very much reproducable if you have a similar resolution and setup. Q. What's happening? -> I have a habit of customizing LO shortkeys the way I can easily remember. So I go to Tools > Customize. Unlike other options menu windows (for example: Tools > Options), "Customize" window is different. Different because the three options which are at the bottom are cropped and hidden. These three options are: - Reset - Cancel - Ok These three options are well protected and untouchable. 4 out of 5 times I will be in this situation stuck whenever I try to apply a shortkey that I want. Sometimes either by luck or by God's grace, I manage to shake Customize window so hard, BOOM, I can see those three options. But at that time, I can't see the Title bar of the "Customize" window which has the option to close the Window. I'm stuck either way. My god, it's THAT annoying. I think this is more of a "GNOME" problem for not recognizing all sorts of screen resolutions. But I can't say this for sure. For some reason, I'm only 95% sure, this is really a GNOME's problem. Whoever problem it is, it is a problem. And it is seriously affecting LibreOffice in particular. I have not seen this sort of problem anywhere else. Please fix it. So far I love LO. Note that: Try to reproduce this issue on the "Customize" option. Not all option's windows is a big as Customize window if you compare with the height. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146674] Duplex dropdown list in the Generic Printer's Paper tab is not translatable
https://bugs.documentfoundation.org/show_bug.cgi?id=146674 Kevin Suo changed: What|Removed |Added OS|All |Linux (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146674] New: Duplex dropdown list in the Generic Printer's Paper tab is not translatable
https://bugs.documentfoundation.org/show_bug.cgi?id=146674 Bug ID: 146674 Summary: Duplex dropdown list in the Generic Printer's Paper tab is not translatable Product: LibreOffice Version: 7.2.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com Steps to Reproduce: 1. Switch to a non-English UI. 2. Go to File > Printer Settings > Properties 3. Click the Duplex dropdown in the Paper tab. Current Result: Simplex, Off, Short Edge, Long Edge. They are not translatable on the UI. Expected: These strings in the dropdown should be translatable on the UI. Version: 7.2.4.1 / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: zh-CN (zh_CN.UTF-8); UI: zh-CN Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146420] LIBO 7.3-0-1 Calc crashes on all linux rpm versions
https://bugs.documentfoundation.org/show_bug.cgi?id=146420 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 142818] LO Writer: Convert table to text leads to massive indents
https://bugs.documentfoundation.org/show_bug.cgi?id=142818 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 142818] LO Writer: Convert table to text leads to massive indents
https://bugs.documentfoundation.org/show_bug.cgi?id=142818 --- Comment #3 from QA Administrators --- Dear Dominik Rüth, 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 108957] [META] AutoCaption bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108957 Bug 108957 depends on bug 142527, which changed state. Bug 142527 Summary: Add caption category "LibreOffice Writer Listing" https://bugs.documentfoundation.org/show_bug.cgi?id=142527 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142527] Add caption category "LibreOffice Writer Listing"
https://bugs.documentfoundation.org/show_bug.cgi?id=142527 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 142527] Add caption category "LibreOffice Writer Listing"
https://bugs.documentfoundation.org/show_bug.cgi?id=142527 --- Comment #3 from QA Administrators --- Dear Olivier Hallot, 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 143326] Crash in: google_breakpad::ExceptionHandler::HandlePureVirtualCall() FILESAVE
https://bugs.documentfoundation.org/show_bug.cgi?id=143326 --- Comment #6 from QA Administrators --- Dear rik, 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 111591] [META] File sending bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=111591 Bug 111591 depends on bug 138316, which changed state. Bug 138316 Summary: sending email through Mailspring (Linux) provides input/output error https://bugs.documentfoundation.org/show_bug.cgi?id=138316 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138316] sending email through Mailspring (Linux) provides input/output error
https://bugs.documentfoundation.org/show_bug.cgi?id=138316 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 138316] sending email through Mailspring (Linux) provides input/output error
https://bugs.documentfoundation.org/show_bug.cgi?id=138316 --- Comment #4 from QA Administrators --- Dear algrinin, 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 129854] Safe mode dialog - translation problems
https://bugs.documentfoundation.org/show_bug.cgi?id=129854 --- Comment #3 from QA Administrators --- Dear Dagmara, 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 146184] Copying text from Calc to Writer will not copy the right font size (gtk3?)
https://bugs.documentfoundation.org/show_bug.cgi?id=146184 Deep17 changed: What|Removed |Added CC||deepoose2...@gmail.com --- Comment #2 from Deep17 --- I can confirm the issue in Version: 7.2.5.2 (x64) / LibreOffice Community Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded and Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 3a683edd9c77e20255357879fc70ce49c9217fa8 CPU threads: 4; OS: Windows 10.0 Build 19042; 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 146673] New: H2 database can no longer be used with LibreOffice Base facilities
https://bugs.documentfoundation.org/show_bug.cgi?id=146673 Bug ID: 146673 Summary: H2 database can no longer be used with LibreOffice Base facilities Product: LibreOffice Version: 6.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: morc...@gmail.com Created attachment 177421 --> https://bugs.documentfoundation.org/attachment.cgi?id=177421=edit UI showing only INFORMATION_SCHEMA tables but not others After upgrading H2 from Ver.1.4.200 to Ver.2.0.206, I found that when connecting to an H2 database, LibreOffice only displays INFORMATION_SCHEMA, and does not show tables in the PUBLIC schema at all. As a result, I can only use SELECT * FROM PUBLIC.PERSON either manually or in a query, but PUBLIC tables do not appear anywhere in the GUI. It turns out that all tables of the BASE TABLE type are being ignored by Libreoffice. I reported it at https://github.com/h2database/h2database/issues/3351, and heard back that it is a KNOWN ISSUE. @katzyn commented that "In the SQL Standard there are various table types: BASE TABLE, VIEW, GLOBAL TEMPORARY, LOCAL TEMPORARY, SYSTEM VERSIONED and database systems can also report other types due to their own reasons." Best, M -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 John changed: What|Removed |Added Keywords||dataLoss -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146671] : SORT changes data rounding
https://bugs.documentfoundation.org/show_bug.cgi?id=146671 m.a.riosv changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED CC||miguelangelrv@libreoffice.o ||rg -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141869] Rephrase "Insert Reference To" items
https://bugs.documentfoundation.org/show_bug.cgi?id=141869 --- Comment #12 from Eyal Rozenberg --- (In reply to Jean-Baptiste Faure from comment #11) Ok, sorry for the hassle, I've replicated this. Now I just need to figure out where that string is and add another patch :-( -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #13 from Telesto --- (In reply to Telesto from comment #12) > I'm able to reproduce comment 10 steps 1-3 FWIW: the range matches bug 146663 and similar behaviour. So expect it to be the same thing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146669] Function request: Calc equivalent of Excel "Converting Decimal Degrees..."
https://bugs.documentfoundation.org/show_bug.cgi?id=146669 --- Comment #3 from Mike Kaganski --- Just a guess: is that https://docs.microsoft.com/en-us/office/troubleshoot/excel/convert-degrees-minutes-seconds-angles that you meant, which lists two functions that "Microsoft provides programming examples for illustration only"? Have you tries to use them as is - Convert_Degree just work (even though it has a useless "With Application" and "End With" lines, that are not used, but still don't prevent it from working). Convert_Decimal from there exposes a bug which I just filed - and only needs to add Trim() around everything inside CDbl calls to work correctly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #12 from Telesto --- I'm able to reproduce comment 10 steps 1-3 Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1bb0e177124d5d6661b72df6c7d848fb23639652 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL Versie: 5.1.6.2 Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909 CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: GL; Locale: nl-NL (nl_NL); Calc: CL Versie: 5.0.6.3 (x64) Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa Locale: nl-NL (nl_NL) but not with 4.4.7.2 However this looks like a different topic in comparison to the initial report in comment 0 (or I simply misread it) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146672] New: CDbl(" 28 ") errors out
https://bugs.documentfoundation.org/show_bug.cgi?id=146672
Bug ID: 146672
Summary: CDbl(" 28 ") errors out
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: BASIC
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: mikekagan...@hotmail.com
CDbl("28 ") gives "Inadmissible value or data type. Data type mismatch."
Cf. to CInt("28 ") which succeeds.
Note also that VBA handles such a string correctly.
Tested with Version: 7.3.0.1 (x64) / LibreOffice Community
Build ID: 840fe2f57ae5ad80d62bfa6e25550cb10ddabd1d
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146669] Function request: Calc equivalent of Excel "Converting Decimal Degrees..."
https://bugs.documentfoundation.org/show_bug.cgi?id=146669 --- Comment #2 from Mike Kaganski --- (In reply to G Whittaker from comment #0) > to Degrees/Minutes/Seconds Ah - of course RADIANS/DEGREES is not about Minutes/Seconds. But curiously, since degree/minute/second uses sexagesimal system, you may create a simple *custom* function (obviously, the "VBA custom function" you refer to is, as its description in comment 0 implies, *custom* - i.e., created by someone in some spreadsheet - it's not an Excel feature?). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146671] : SORT changes data rounding
https://bugs.documentfoundation.org/show_bug.cgi?id=146671 rossni...@gmail.com changed: What|Removed |Added Severity|normal |trivial -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146671] : SORT changes data rounding
https://bugs.documentfoundation.org/show_bug.cgi?id=146671 --- Comment #1 from rossni...@gmail.com --- I think I've solved it. The extra 0:00.5 is from a cell $N$4. When I sort the column, this cell position becomes empty. I'll have to figure out a better way of adding the 0.00.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of cells with wrapped text is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #10 from Tobias Leupold --- This is actually right ;-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of cells with wrapped text is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 Tobias Leupold changed: What|Removed |Added Summary|Height of line-breaked |Height of cells with |cells is lost after saving, |wrapped text is lost after |depending on the column |saving, depending on the |width |column width -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146671] New: : SORT changes data rounding
https://bugs.documentfoundation.org/show_bug.cgi?id=146671 Bug ID: 146671 Summary: : SORT changes data rounding Product: LibreOffice Version: 7.2.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rossni...@gmail.com In my spreadsheet I have a column which calculates my running pace as mm:ss. Today's run had an average pace of 6:20.625 The formula correctly rounds this to 6:21. When I sort the column, it shows 6:20 instead. My formula is time (HH:MM:SS) / distance (0.00) + 0.00.5 (M:SS.0) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #9 from LeroyG --- Maybe the title must be changed. A line break in a cell is set with Ctrl+Enter (not the case here). Wrap Text is the issue here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #8 from LeroyG --- More: - Open the 18 cm column width sample file (https://bugs.documentfoundation.org/attachment.cgi?id=177419) - Paste "111 222 333 444 555 666 777 888 999 000 111 222 333" in A2 - Set Wrap Text - Change the zoom level Actual result: The second 222 group changes from first to second line depending on zoom level. But, after reload, Wrap Text is not lost for this cell. Version: 7.1.8.1 (x64) / LibreOffice Community Build ID: e1f30c802c3269a1d052614453f260e49458c82c CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: es-MX (es_ES); UI: en-US Calc: CL Skia is not enabled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146669] Function request: Calc equivalent of Excel "Converting Decimal Degrees..."
https://bugs.documentfoundation.org/show_bug.cgi?id=146669 --- Comment #1 from Mike Kaganski --- (In reply to G Whittaker from comment #0) > "Microsoft Excel Visual Basic for Applications custom function Converting > Decimal Degrees to Degrees/Minutes/Seconds", and its converse. Could you please mention what that function name is in VBA, and where its documentation is? Otherwise, you may use all spreadsheet functions in Basic, using respective interface [1]. That includes RADIANS [2] and its converse DEGREES [3]. [1] https://help.libreoffice.org/7.2/en-US/text/sbasic/shared/calc_functions.html?=BASIC [2] https://help.libreoffice.org/7.2/en-US/text/scalc/01/04060106.html?DbPAR=CALC#bm_id3144702 [3] https://help.libreoffice.org/7.2/en-US/text/scalc/01/04060106.html?DbPAR=CALC#bm_id3145314 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146662] Have new Writer documents open in Entire page zoom
https://bugs.documentfoundation.org/show_bug.cgi?id=146662 --- Comment #1 from LeroyG --- Zoom level and view layout are saved in each document. New documents zoom level is affected by the last zoom level you set to an open document. Tested with LibreOffice 7.0.6.2 (x64); OS: Windows 10.0. (https://ask.libreoffice.org/t/i-want-to-set-the-default-view-layout-to-100/64771/5?u=leroyg) Also tested with: Version: 7.1.8.1 (x64) / LibreOffice Community Build ID: e1f30c802c3269a1d052614453f260e49458c82c CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: es-MX (es_ES); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146670] Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=146670 Julien Nabet changed: What|Removed |Added Ever confirmed|0 |1 OS|All |Windows (All) CC||serval2...@yahoo.fr Status|UNCONFIRMED |NEEDINFO Version|unspecified |6.2.0.3 release --- Comment #1 from Julien Nabet --- Please give a try to a recent LO version 7.1.8 or 7.2.5 Indeed, 6.2.0.3 is quite old. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 --- Comment #4 from John --- All of images were linked images, and were anchored as characters. Here is a comparision of the XML markup of the image that is still in the file and the XML of the image that is now missing: _This is a part of "covid.jpg" image. This image is OK, it wasn't removed._ ```xml ``` _And this is a part of the "house.jpg" image. This image is missing:_ ```xml ``` It is very clear that the second snippet is broken. The only question is why. All of the images were inserted exactly the same way, by clicking the "Insert > Image" and enabling the "Link" check box. After the document was almost ready, I closed it, and then opened it again to edit some text. I have do it multiple times and the images were in their correct places. Then, two days ago, I opened this document again, and the images were missing, and XML markup is broken. It seems there was some internal error during the last save. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38093] Add an Outline View layout and editing mode to Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=38093 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6667 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146667] Code Folding in the BASIC IDE's editor
https://bugs.documentfoundation.org/show_bug.cgi?id=146667 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||rayk...@gmail.com, ||vstuart.fo...@utsa.edu Summary|Code Folding in Code Editor |Code Folding in the BASIC ||IDE's editor Keywords||needsUXEval See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=38 ||093 Version|7.2.4.1 release |Inherited From OOo --- Comment #1 from V Stuart Foote --- +1, and might be able to reuse some of the work needed for SB outline folding done for Writer? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142719] AUTO CORRECT: Undo adds exception of two initial capitals to exception list
https://bugs.documentfoundation.org/show_bug.cgi?id=142719 sdc.bla...@youmail.dk changed: What|Removed |Added CC||sdc.bla...@youmail.dk --- Comment #9 from sdc.bla...@youmail.dk --- (In reply to Caolán McNamara from comment #6) > As far as I can tell this is intentional. If the user undos the "two initial > capitals" autocorrect (as the next thing the user does after the > autocorrect) then a new persistent rule is added to not do that autocorrect > again. I see the code for this exists back in the "Initial import" from 2000. This is true is if (a) "autoinclude" is enabled on Tools - AutoCorrect - AutoCorrect Options - Exceptions tab, and (b) Tools - AutoCorrect - While Typing is enabled. It is even documented: https://help.libreoffice.org/latest/en-US/text/shared/01/06040300.html#bm_id6384777 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146670] New: Crash in: mergedlo.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=146670 Bug ID: 146670 Summary: Crash in: mergedlo.dll Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: thomkenn...@hotmail.com This bug was filed from the crash reporting server and is br-f9d91d91-73b4-460f-a6dd-4efd0b0c0612. = Opened existing LibreCalc file which had been saved in .xlsx format. File contains a few columns of data and 2 charts based on that data. On each chart are a number of text boxes. I selected one text box, Ctrl-C, Ctrl-V, then double-click to edit text, then click outside the text box to de-select. It was shortly after this last operation that the crash occurred. This has happened a number of times after reopening the original (non-recovered) file and repeated the above sequence. Subsequent crashes did not occur at the same point in editing. The same problem occurs when editing a recently saved .ods file (saved from the .xlsx ver.) Ref: crashreport.libreoffice.org/stats/crash_details/7e271737-d790-457f-a334-9f5da34abc5a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146661] Linked images are missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146661 --- Comment #3 from John --- And the following bullshit is from LibreOffice Facebook official page: > Using the wrong office suite could cost you your job! Check > out this post from Twitter – someone is locked out of their > documents in Microsoft Office. This happens a lot. > > But this wouldn't happen with LibreOffice! Our software > respects your freedom and privacy, and doesn't lock you in. > Help us spread the word about our free office suite, used > by millions around the world <...> One of the user there commented: > I love LibreOffice, but see no need to shit-talk your competitor... And the LO folks who manage the page answer: > If a product locks people out of their OWN documents, even > when they've paid for it, that's not "sh*t-talking" – that's > pointing out how terrible that situation is! LibreOffice > stands on its own feet and we don't normally talk about > proprietary products, but it's important to make people aware > that there's an alternative... But of course, they won't say you that Writer will silently harm your documents. That it can silently remove the formatting or images. And that you will not be even aware about this until you open the documents later. And these documents, of course, can be very valuable. So, open-source folks blame Microsoft for the FUD propaganda, but the same FUD propaganda, mixed with a quasi-religious bullshit aka "help them to spreading the word" is what they use to promote their buggy crapware. And using LO is not really "free" for us, users. Saying that "LO doesn't cost you money, so you users cannot blame it" is bullshit. When you, developers and managers, know that your software have _so_ many bugs and _so_ many bugs have critical impact to the workflow, and these bugs are so easy for users to face with them, it is just unfair to promote your software as something that is ready for end-users, you simply lie them. They trust you, they think that "stable" releases are really stable (but in fact these releases are alpha ones) and "fresh" releases are unstable just a little (these releases are in fact pre-alpha ones), they spend days and weeks testing and reporting dozens and hundreds of bugs, they spend days and weeks fixing their broken documents because they hope that this nightmare is something occasional and temporary. But no, it is neither occasional nor temporary. I leave this message here not because I think it has any value to you, of course. But because it will be a good reminder for myself. And because it will be possible to provide a link to people who are thinking about to start using LO. I really don't care whether you ban me or not. But if someone think that I'm "just a random guy who never really tried LO", he/she can check the bugs I have reported for several years. There are many of them. I also have 2 additional account, so you can multiply this number by 3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121584] Ctrl+LShift, Ctrl+RShift not setting direction in comments
https://bugs.documentfoundation.org/show_bug.cgi?id=121584 --- Comment #5 from Eyal Rozenberg --- Bug still manifests with: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 250e4886d85a7e131da76f181b3fa7be02d1a76d CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120615] Ctrl+LShift, Ctrl+RShift not setting direction in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=120615 --- Comment #9 from Eyal Rozenberg --- Bug still manifests with: Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 250e4886d85a7e131da76f181b3fa7be02d1a76d CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106899] Unicode Index Entries that are not English is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=106899 Andreas Heinisch changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |andreas.heini...@yahoo.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146669] New: Function request: Calc equivalent of Excel "Converting Decimal Degrees..."
https://bugs.documentfoundation.org/show_bug.cgi?id=146669 Bug ID: 146669 Summary: Function request: Calc equivalent of Excel "Converting Decimal Degrees..." Product: LibreOffice Version: 4.0.0.3 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gmwhit...@yahoo.co.uk Description: Unable to find Calc equivalent of: "Microsoft Excel Visual Basic for Applications custom function Converting Decimal Degrees to Degrees/Minutes/Seconds", and its converse. Re-opened request from many years ago! This function is increasingly used in GPS map references, navigation, and astronomy. I currently use an old scientific calculator to do the conversions in both directions, then type the data into Calc. I am considering changing to Excel to automate this process, saving time. Please add this function to Calc, or if already present please update Help. Steps to Reproduce: 1.N/A 2. 3. Actual Results: N/A Expected Results: N/A Reproducible: Always User Profile Reset: No Additional Info: Requested: Compatibility with current Excel for converting Decimal Degrees to Degrees/Minutes/Seconds, and vice versa. Nothing relevant found in LibreOffice Help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 90497] Implementing document themes
https://bugs.documentfoundation.org/show_bug.cgi?id=90497 --- Comment #20 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9754b3feb4092243f30c665abc0344b1a665b5f6 tdf#90497 Replace Open Sans -> Noto Sans It will be available in 7.4.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.
[Libreoffice-bugs] [Bug 90497] Implementing document themes
https://bugs.documentfoundation.org/show_bug.cgi?id=90497 Commit Notification changed: What|Removed |Added Whiteboard|target:5.3.0 target:5.2.2 |target:5.3.0 target:5.2.2 ||target:7.4.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146415] Allow Basic + "Extended" Dictionaries
https://bugs.documentfoundation.org/show_bug.cgi?id=146415 Dieter changed: What|Removed |Added Whiteboard|t | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #7 from Tobias Leupold --- PS: Maybe this is still or again the problem from Bug #49255, but this one has been filed and fixed almost a decade ago. I just found it whilst researching the possible cause for this bug here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146415] Allow Basic + "Extended" Dictionaries
https://bugs.documentfoundation.org/show_bug.cgi?id=146415 Dieter changed: What|Removed |Added CC||dgp-m...@gmx.de Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Whiteboard| QA:needsComment|t --- Comment #1 from Dieter --- It's already possible to create new dictionaries with Tools => Spelling => Options. Does this solve your problem? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141869] Rephrase "Insert Reference To" items
https://bugs.documentfoundation.org/show_bug.cgi?id=141869 --- Comment #11 from Jean-Baptiste Faure --- (In reply to Eyal Rozenberg from comment #10) > [...] > I don't get any tooltip when my mouse is on the selection list. Perhaps if > you could clarify the previous step? Did you activate **Extended** Tooltips in menu Tools > Options > LibreOffice > General? Best regards. JBF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145967] An infobar should notify user that some embedded fonts couldn't be used because of license restrictions
https://bugs.documentfoundation.org/show_bug.cgi?id=145967 Ramreiso Kashung changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |ramreiso...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #6 from Tobias Leupold --- Created attachment 177420 --> https://bugs.documentfoundation.org/attachment.cgi?id=177420=edit The 17 cm column width saved file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #5 from Tobias Leupold --- Created attachment 177419 --> https://bugs.documentfoundation.org/attachment.cgi?id=177419=edit The 18 cm column width saved file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #4 from Tobias Leupold --- Created attachment 177418 --> https://bugs.documentfoundation.org/attachment.cgi?id=177418=edit Example with a column width of 17 cm after saving, closing and re-opening -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #3 from Tobias Leupold --- Created attachment 177417 --> https://bugs.documentfoundation.org/attachment.cgi?id=177417=edit Example with a column width of 17 cm before saving -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #2 from Tobias Leupold --- Created attachment 177416 --> https://bugs.documentfoundation.org/attachment.cgi?id=177416=edit Example with a column width of 18 cm after saving, closing and re-opening -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 --- Comment #1 from Tobias Leupold --- Created attachment 177415 --> https://bugs.documentfoundation.org/attachment.cgi?id=177415=edit Example with a column width of 18 cm before saving -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146668] New: Height of line-breaked cells is lost after saving, depending on the column width
https://bugs.documentfoundation.org/show_bug.cgi?id=146668 Bug ID: 146668 Summary: Height of line-breaked cells is lost after saving, depending on the column width Product: LibreOffice Version: 7.1.6.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: t...@l3u.de Description: When declaring a cell as line-breaking, and the contained text is displayed in two lines, the height is (depending on the width of the respective column) lost after saving the file, closing it and re-opening it. After reopeing a file in such a case, the row's height is set to the default height, and the text (which is still line-breaking) is clipped. Steps to Reproduce: - Using the binary LibreOffice 7.1.7.2 package on Gentoo Linux, use Liberation Sans 10 pt (the default font setting) - Type "aaa ee f gg hhh " in cell A1 - Set the width for column A to 18 cm - Enable automatic line breaking for cell A1 (the text is displayed in two lines, the "" appears in the second line) - Save the file and close it - Open the file Actual Results: Row 1's height is set to the default height, but the cell A1's text is still line-breaked. This leads to the text being clipped Expected Results: The height row 1 had when the file was saved should be preserved, no text should be clipped Reproducible: Always User Profile Reset: No Additional Info: Interestingly, this only happens for specific column widths: If one sets the width of column A to 17 cm (instaead of 18), the visible result is the same, "" is displayed in a second line. But, in this case, after saving and re-opening the file, the height of row 1 is restored correctly, and no clipping happens. See the screenshots I'll attach! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143601] French Langpack for 7.1.5 and 7.2.0.4 invalid causing installation to fail
https://bugs.documentfoundation.org/show_bug.cgi?id=143601 --- Comment #23 from MG --- i cannot understand why the problem listed for a long time is still present -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106899] Unicode Index Entries that are not English is ignored.
https://bugs.documentfoundation.org/show_bug.cgi?id=106899 Andreas Heinisch changed: What|Removed |Added CC||andreas.heini...@yahoo.de --- Comment #7 from Andreas Heinisch --- Still present in: Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: f344df3721b3fc5c9657fe5f7dce26af45de7bc6 CPU threads: 6; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: CL Should we detect the charset in the .sid-file? Or should we just assume that the files are in utf8. I tested it and it seems LO writes these files in utf8 without BOM. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143601] French Langpack for 7.1.5 and 7.2.0.4 invalid causing installation to fail
https://bugs.documentfoundation.org/show_bug.cgi?id=143601 --- Comment #22 from MG --- The problem is still present whith the actual version 7.2.5.2 !! Installing the french version says the version 7.2.5.2 is not a VALID VERSION !!! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace dialog changes position when reopened (gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 V Stuart Foote changed: What|Removed |Added Summary|Find and Replace doesn't|Find and Replace dialog |restore last user position |changes position when |when opened |reopened (gtk3) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116828] edit comments are done in place when there are frozen columns, making it invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=116828 --- Comment #7 from paj...@gmail.com --- This still happens in version 7.2.4.1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146667] New: Code Folding in Code Editor
https://bugs.documentfoundation.org/show_bug.cgi?id=146667 Bug ID: 146667 Summary: Code Folding in Code Editor Product: LibreOffice Version: 7.2.4.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: krys...@tlhea.org Created attachment 177414 --> https://bugs.documentfoundation.org/attachment.cgi?id=177414=edit A visual example of code folding from notepad++ for your reference Please add code folding to the macro editor. Code folding is the ability to collapse portions of the code to both unclutter and speed up the code editing process by hiding the portions of code you aren't working on. for instance: sub realylongsub() ... ... --- end sub sub nextsub when folded, becomes +sub reallylongsub() sub nextsub() ... end sub. image of an example as seen in notepad++ are included as an example. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 Dave Barton changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Severity|normal |minor --- Comment #7 from Dave Barton --- CONFIRMED with the "official" LibreOffice 7.2.5.2 Linux installation. Closing the dialog's close button retains the dialog's last position, reopening the dialog after closing the dialog with ESC key or the title bar close button positions the dialog center screen Unable to replicate the issue with LO 7.2.5.2 under Windows 10. Maybe an "Easy Hack"? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145789] PDF import: Kaplan-Meier survival curves not properly captured
https://bugs.documentfoundation.org/show_bug.cgi?id=145789 Alberto changed: What|Removed |Added CC||alberto.carmonabayonas@gmai ||l.com --- Comment #2 from Alberto --- Created attachment 177413 --> https://bugs.documentfoundation.org/attachment.cgi?id=177413=edit Another example of poor performance of libreoffice LibreOffice definitely performs poorly when there are many dots or lines in the image, which is almost always the case, so I will to switch to other alternatives. I am attaching another example so if anyone is ever interested in correcting these errors. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 --- Comment #6 from V Stuart Foote --- (In reply to R. Green from comment #5) > I see what's happening now. F follows last user position on launching IF > it was last closed with the "Close" button. But IF you close it with the X > (cross icon) instead, it next opens in the default position. Pressing [ESC] > leads to the same issue. > > AFAIK, the launch behaviour should be the same (i.e. last user position) no > matter how you last closed the F window. On Windows builds can not confirm, it makes no difference on how the dialog is dismissed: 'Close' button, , or the frames CSD 'X' button -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140866] Cell comments disappear
https://bugs.documentfoundation.org/show_bug.cgi?id=140866 --- Comment #13 from PaulSh --- After some more testing, it seems that my above methodology can also trash the comments if a drawing object (e.g. a text box) is copy/pasted. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #11 from John --- Created attachment 177412 --> https://bugs.documentfoundation.org/attachment.cgi?id=177412=edit cursor and virtual space -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #10 from John --- To both @Mike and @Telesto I just found a reliable way to reproduce the "3rd line stay bold" issue. There are no tralining spaces or Shift+Enter keypresses, but you need to be careful and patient. Actually, it happens quite often and there are probably many other ways to reproduce it. 0. restart Writer in safe mode 1. type the text ``` Lorem ipsum dolor sit amet Lorem ipsum Lorem ipsum Lorem ipsum dolor sit amet ``` 2. type a space character in the very end of the 3rd line, put the cursor before the space, then press Shift+Home and Ctrl+B, and then remove the space (by pressing End and then Backspace). 3. select the whole text and apply some paragraph style (e.g., Ctrl+0 to apply Text Body) you will see that the 3rd line is now regular, not bold. # But now the second part. Repeat steps 2 and 3. You will see that the 3rd line is now preserved bold. But this not REALLY true. At least for me on Windows. This is just wrong rendering. Scroll the page past the text and then back and you will see that the 3rd line is now regular. What is strange, though, is that if you place the cursor on the very end of the 3rd line, you will see like you have a space before it. (See the image.) But this space is not real. If you press the Backspace key, it will remove both the virtual space and the letter m. What the heck. OK, type the missing "m". # The third part. Repeat steps 2 and 3. You will see that the 3rd line is now preserved bold. And it stay bold no matter what you do. This is not just rendering. It is really bold. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114369] Label workflow requires simplification
https://bugs.documentfoundation.org/show_bug.cgi?id=114369 --- Comment #9 from Fred Olness --- (In reply to Buovjaga from comment #1) > Yep, it is a bit convoluted. Here is a video tutorial for reference: > https://www.youtube.com/watch?v=7n8Psg8yxPE Right, BUT this video does NOT show how to deal with blank lines, which is the KEY POINT!!! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146666] New: Writer: Duplex print not working
https://bugs.documentfoundation.org/show_bug.cgi?id=14 Bug ID: 14 Summary: Writer: Duplex print not working Product: LibreOffice Version: 7.2.4.1 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: blandyna.bog...@gmail.com Description: Duplex print in Writer not working as duplex. The pages were rotated, but nod printed on the back side. I wanted to print 4 sites with duplex = 2 pages paper. After the print I had 4 pages paper. Printer: HP LaserJet 1320 with duplex. Writer: 7.2.5.2 Steps to Reproduce: 1. Document in Writer with more than 1 page. 2. CTRL + P: Duplex on long side. 3. Actual Results: Duplex not wirking. Expected Results: Duplex is working. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 7.2.5.2 (x64) / LibreOffice Community Build ID: 499f9727c189e6ef3471021d6132d4c694f357e5 CPU threads: 6; OS: Windows 10.0 Build 19043; UI render: Skia/Vulkan; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102847] [META] Quick Find, Search and Replace
https://bugs.documentfoundation.org/show_bug.cgi?id=102847 Bug 102847 depends on bug 146647, which changed state. Bug 146647 Summary: [UI] Reword for Match in the Find and Replace dialog https://bugs.documentfoundation.org/show_bug.cgi?id=146647 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146647] [UI] Reword for Match in the Find and Replace dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=146647 LeroyG changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146665] New: Crash in: SfxSetItem::GetItemSet()
https://bugs.documentfoundation.org/show_bug.cgi?id=146665 Bug ID: 146665 Summary: Crash in: SfxSetItem::GetItemSet() Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: exwa...@aol.com This bug was filed from the crash reporting server and is br-99c67709-6145-4569-80b4-bd28b93c1c8a. = Calc shuts down after adding data to a table, and selecting 'DELETE' on its Pivot Table sheet before generating a new pivot table to reflect the added data. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112948] Default outline still uses StarSymbol font
https://bugs.documentfoundation.org/show_bug.cgi?id=112948 --- Comment #3 from phv --- Why does LibreOffice still use the StarSymbol font, even though there is a fallback to the OpenSymbol font, for the default list in Draw? Is it worth opening a new report for this issue? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142032] FEATURE REQUEST: Customize Tabbed Compact UI toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=142032 --- Comment #6 from bugs.documentfoundation-sa...@balkonien.org --- Hi, I am affected by this as well. Especially when you use Add-Ons which add their own buttons to toolbars it is a waste of screen area that they are displayed in a toolbar unter the notebook bar. It would be awesome if the tabbed UI could be customized. Best regards Samuel -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142032] FEATURE REQUEST: Customize Tabbed Compact UI toolbars
https://bugs.documentfoundation.org/show_bug.cgi?id=142032 bugs.documentfoundation-sa...@balkonien.org changed: What|Removed |Added Summary|Cannot customize neither|FEATURE REQUEST: Customize |the Tabbed Compact UI |Tabbed Compact UI toolbars |toolbars neither their | |buttons | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #9 from Mike Kaganski --- (In reply to Telesto from comment #7) > Maybe start with an example where you prefer Paragraph DF instead of a > Paragraph Style or Character DF. That's surely helpful for grasping this.. Heh, so you suggest *me* to "start with" something that you did not explain?! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #8 from Mike Kaganski --- (In reply to Telesto from comment #6) Are you confirming my comment 5? It would be nice if you described your screencast - what it shows, what to watch. But I suppose it shows exactly what I wrote. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #7 from Telesto --- (In reply to Mike Kaganski from comment #5) > I do not understand what you mean: do you say you do not understand the > concept of paragraph DF, or you do not understand why it includes pieces > shared with character DF, or if you do not understand why it gest applied in > *this specific case*. The last is just a UX choice of early days; and it *in > theory* could be changed, although it could be unexpected to most; the idea > behind that decision was to avoid dedicated workflow for paragraph DF vs > character DF application. But the first two points are absolutely logical > concepts, and part of the standard, meaning it is simply nothing to discuss > here. Maybe start with an example where you prefer Paragraph DF instead of a Paragraph Style or Character DF. That's surely helpful for grasping this.. * When using formatting like CTRL+B I (personally) expect "Character DF" all the time. Currently I control or Character DF or Paragraph DF depending on select area. Which requires lots of awareness of the selected area. And there is no-feedback if we go from Character DF to Paragraph DF or not (OK, Style Inspector) If I press CTRL+B at start of the first paragraph, doesn't mean I intend to write full paragraph in BOLD (which makes paragraph DF the obvious choice). Maybe I wanted to start with first word to be bold.. Result being; having Paragraph DF bold & override by Character DF non-bold. * There is now way to remove Paragraph DF (except for clear all DF, which is really rigorous) * In the case here the user wanted to apply Paragraph Style, and assumed the applied formatting being Character DF. Where Character DF would override Paragraph Style. However caused by auto-application of Paragraph DF this whole idea broke down. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146058] LibreOffice window takes long time to show up after upgrade to Fedora 35
https://bugs.documentfoundation.org/show_bug.cgi?id=146058 Julian Sikorski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #10 from Julian Sikorski --- Seems to be fixed as of 7.2.5.2. *** This bug has been marked as a duplicate of bug 146219 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #6 from Telesto --- Created attachment 177407 --> https://bugs.documentfoundation.org/attachment.cgi?id=177407=edit Screencast -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146648] Find and Replace doesn't restore last user position when opened
https://bugs.documentfoundation.org/show_bug.cgi?id=146648 --- Comment #5 from R. Green --- I see what's happening now. F follows last user position on launching IF it was last closed with the "Close" button. But IF you close it with the X (cross icon) instead, it next opens in the default position. Pressing [ESC] leads to the same issue. AFAIK, the launch behaviour should be the same (i.e. last user position) no matter how you last closed the F window. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146663] DOCX: Applying paragraph styles resets Character direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146663 --- Comment #1 from Mike Kaganski --- I would assume it was some convenience change, trying to detect that some character DF spans the whole paragraph, and treat it as it's paragraph DF ... but yes, bibisect could answer. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 --- Comment #5 from Mike Kaganski --- (In reply to John from comment #0) > The 3rd line ... are still bold. I do not reproduce this. The third line is not bold in Version: 7.3.0.1 (x64) / LibreOffice Community Build ID: 840fe2f57ae5ad80d62bfa6e25550cb10ddabd1d CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL as well as in Version: 7.0.0.3 (x64) Build ID: 8061b3e9204bef6b321a21033174034a5e2ea88e CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: CL The cited line could *only* be true in case when the "Put the cursor in the very **end** of the 3rd line" piece of steps were performed incorrectly, e.g. the third line contained a trailing space, and the selection didn't include that space. Or maybe the third and the fourth lines were not separate paragraphs, but split by line break (Shift+Enter). In both cases, the selection then would not cover the whole paragraph. (In reply to Telesto from comment #4) > I'm not seeing the advantage of "Paragraph DF formatting", in my perception it > should simply be "Character DF". I do not understand what you mean: do you say you do not understand the concept of paragraph DF, or you do not understand why it includes pieces shared with character DF, or if you do not understand why it gest applied in *this specific case*. The last is just a UX choice of early days; and it *in theory* could be changed, although it could be unexpected to most; the idea behind that decision was to avoid dedicated workflow for paragraph DF vs character DF application. But the first two points are absolutely logical concepts, and part of the standard, meaning it is simply nothing to discuss here. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146664] Image jumps to different page at undo
https://bugs.documentfoundation.org/show_bug.cgi?id=146664 --- Comment #1 from Telesto --- Different steps 1. Select image 25 (navigator) 2. CTRL+X 3. CTRL+Z -> At wrong spot 5. Click some different image on the same page CTRL+X CTRL+Z Image 25 jumps back in 3.5.7.2 not in 7.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146664] Image jumps to different page at undo
https://bugs.documentfoundation.org/show_bug.cgi?id=146664 Telesto changed: What|Removed |Added Keywords||bibisectRequest, regression -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146664] New: Image jumps to different page at undo
https://bugs.documentfoundation.org/show_bug.cgi?id=146664 Bug ID: 146664 Summary: Image jumps to different page at undo Product: LibreOffice Version: 4.0.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Image jumps to different page at undo Steps to Reproduce: 1. Open the attached file 2. Go to page 3, select the image with red border 3. CTRL+X 4. CTRL+Z Actual Results: Image moves to 4 page Expected Results: Opens at 4 page on file open Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1bb0e177124d5d6661b72df6c7d848fb23639652 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL 4.4.7.2 and in 4.0.0.3 but not in LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130687] CRASH: after paste and undo ( table related )
https://bugs.documentfoundation.org/show_bug.cgi?id=130687 --- Comment #5 from Telesto --- No crash Version: 7.4.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1bb0e177124d5d6661b72df6c7d848fb23639652 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146614] Crash swlo!SwFrame::SetInvalidVert+0x4397
https://bugs.documentfoundation.org/show_bug.cgi?id=146614 Telesto changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #6 from Telesto --- Confirming based on BT at bug 146621 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 Telesto changed: What|Removed |Added CC||mikekagan...@hotmail.com, ||tele...@surfxs.nl --- Comment #4 from Telesto --- @Mike I'm not sure what the expect. I'm not seeing the advantage of "Paragraph DF formatting", in my perception it should simply be "Character DF". But well what do I know about styles.. And obviously someone or some code is likely relying on the current behaviour. FWIW: the Paragraph DF formatting will be converted to Character DF on DOCX export (but also has a bug see bug 146663) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146660] Applying paragraph styles resets some direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146660 Telesto changed: What|Removed |Added Version|7.2.4.1 release |Inherited From OOo --- Comment #3 from Telesto --- Also in LibreOffice 3.5.7.2 Build ID: 3215f89-f603614-ab984f2-7348103-1225a5b -- You are receiving this mail because: You are the assignee for the bug.
