[Libreoffice-bugs] [Bug 134426] Changing Paragraph format, editing Text and changing back leaves edited text's format unchanged
https://bugs.documentfoundation.org/show_bug.cgi?id=134426 Justin L changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |jl...@mail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130172] PDF export of a (very) large spreadsheet is rather slow
https://bugs.documentfoundation.org/show_bug.cgi?id=130172 Luboš Luňák changed: What|Removed |Added CC||l.lu...@collabora.com Status|NEW |NEEDINFO --- Comment #4 from Luboš Luňák --- I agree with Noel, please check if this is still valid. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100639] FILEOPEN Page number doesn't display (MS Publisher)
https://bugs.documentfoundation.org/show_bug.cgi?id=100639 Heiko Tietze changed: What|Removed |Added Product|Document Liberation Project |LibreOffice Component|libmspub|filters and storage Version|unspecified |5.1.3.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145104] Accessibility: Paragraph Style "Index" has no language set
https://bugs.documentfoundation.org/show_bug.cgi?id=145104 --- Comment #7 from Heiko Tietze --- (In reply to Mike Kaganski from comment #6) > implement the proper fix and revert the hack - but only in that order :-) Well, a bit too hackish for my taste and I'd change the order. But anyway, I pressed one button, you do the next (submit or abandon *g*) in https://gerrit.libreoffice.org/c/core/+/124705 -- 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 Luboš Luňák changed: What|Removed |Added CC||l.lu...@collabora.com --- Comment #6 from Luboš Luňák --- Either the instructions in comment #1 are unclear, or I cannot reproduce with current master. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96000] [META] Spelling and grammar checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=96000 Bug 96000 depends on bug 143066, which changed state. Bug 143066 Summary: TOC: Give option to switch off spell checking for table of contents https://bugs.documentfoundation.org/show_bug.cgi?id=143066 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 Bug 89606 depends on bug 143066, which changed state. Bug 143066 Summary: TOC: Give option to switch off spell checking for table of contents https://bugs.documentfoundation.org/show_bug.cgi?id=143066 What|Removed |Added Status|VERIFIED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145104] Accessibility: Paragraph Style "Index" has no language set
https://bugs.documentfoundation.org/show_bug.cgi?id=145104 --- Comment #6 from Mike Kaganski --- (In reply to Heiko Tietze from comment #5) > Then let's revert and implement a condition. It is a hack, but still an improvement. Of course, it would be great to implement the proper fix and revert the hack - but only in that order :-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145104] Accessibility: Paragraph Style "Index" has no language set
https://bugs.documentfoundation.org/show_bug.cgi?id=145104 --- Comment #5 from Heiko Tietze --- (In reply to Mike Kaganski from comment #4) > 2. The fix in bug 143066 was indeed just a hack... Then let's revert and implement a condition. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145104] Accessibility: Paragraph Style "Index" has no language set
https://bugs.documentfoundation.org/show_bug.cgi?id=145104 --- Comment #4 from Mike Kaganski --- Two issues here. 1. The accessibility check should not check this for styles. The check itself is *wrong*, since only the actual data must have an assigned unambiguous language, not styles (there may well be legitimate cases to *not* set style languages). 2. The fix in bug 143066 was indeed just a hack: it did not make what the bug asked for (disable the check for the field), but instead relied on some style being used for the field, and not used for anything else, which both may be false in some cases. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 121699] Lots of menu buttons and icons are greyed out and Calc file window cannot be closed
https://bugs.documentfoundation.org/show_bug.cgi?id=121699 Justin L changed: What|Removed |Added OS|Windows (All) |All Hardware|x86-64 (AMD64) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70551] WEEKS() function uses ISO weeknum and is not locale-dependent, which is not explained in the Help
https://bugs.documentfoundation.org/show_bug.cgi?id=70551 Mike Kaganski changed: What|Removed |Added Component|Calc|Documentation CC||olivier.hallot@libreoffice. ||org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145104] Accessibility: Paragraph Style "Index" has no language set
https://bugs.documentfoundation.org/show_bug.cgi?id=145104 Heiko Tietze changed: What|Removed |Added CC||mikekagan...@hotmail.com --- Comment #3 from Heiko Tietze --- Me suggests to resolve NAB, see bug 143066. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145578] The WEEKS() function gives an incorrect answer around January 4th
https://bugs.documentfoundation.org/show_bug.cgi?id=145578 --- Comment #3 from Mike Kaganski --- By the way, this is what also gives WEEKS(d1;d2;1)+WEEKS(d2;d1;1)=1 for most d1 and d2 when they are in different years. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134426] Changing Paragraph format, editing Text and changing back leaves edited text's format unchanged
https://bugs.documentfoundation.org/show_bug.cgi?id=134426 Dieter changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #27 from Dieter --- VERIFIED with Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 742b8befecbcfc0cfab87cfcd87c83b7d8ef32ab CPU threads: 4; OS: Windows 10.0 Build 19043; 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 145254] Language Tool 5.4-5.5--options--hangs--unusable, Writer v 7.1.6.2--manjaro 21.1.6
https://bugs.documentfoundation.org/show_bug.cgi?id=145254 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de --- Comment #1 from Dieter --- I can't confirm this with language Tool 5.4 and Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL So perhaps related to Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103364] [META] Bullet and numbering dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103364 Bug 103364 depends on bug 143254, which changed state. Bug 143254 Summary: "Greek Upper Letter" numbering style should be named "Greek Upper Numeral" https://bugs.documentfoundation.org/show_bug.cgi?id=143254 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145223] crash when copy-pasting (specific) heading
https://bugs.documentfoundation.org/show_bug.cgi?id=145223 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Whiteboard| QA:needsComment| Crash report or||[sw::mark::MarkManager::ren crash signature||ameMark(sw::mark::IMark ||*,rtl::OUString const &)] CC||dgp-m...@gmx.de OS|Linux (All) |All Blocks||133092 --- Comment #2 from Dieter --- I confirm it with Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 742b8befecbcfc0cfab87cfcd87c83b7d8ef32ab CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL and with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL Crash Report: https://crashreport.libreoffice.org/stats/crash_details/e22ce073-2514-492e-9e25-f5ae9bffc27a 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 Dieter changed: What|Removed |Added Depends on||145223 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145223 [Bug 145223] crash when copy-pasting (specific) heading -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145586] Have you ever been to Jaipur? If yes, then you are surely aware of the Jaipur escort service as well.
https://bugs.documentfoundation.org/show_bug.cgi?id=145586 himajin100...@gmail.com changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145586] Have you ever been to Jaipur? If yes, then you are surely aware of the Jaipur escort service as well.
https://bugs.documentfoundation.org/show_bug.cgi?id=145586 himajin100...@gmail.com changed: What|Removed |Added Component|iOS Remote App |deletionRequest Version|2.2.3 |unspecified Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED Product|Impress Remote |LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145586] New: Have you ever been to Jaipur? If yes, then you are surely aware of the Jaipur escort service as well.
https://bugs.documentfoundation.org/show_bug.cgi?id=145586 Bug ID: 145586 Summary: Have you ever been to Jaipur? If yes, then you are surely aware of the Jaipur escort service as well. Product: Impress Remote Version: 2.2.3 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: iOS Remote App Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jaipurs...@gmail.com The welcoming eyes of Jaipur escorts often embrace every individual in Jaipur. The city is full of males, who are alone who like to be with someone grateful to accompany them. They can choose from the lovely girls in town. The whores in Jaipur are beautiful and tempting for lonely men making them the ideal partners. Generally, these hot babes make them happy with the affection and love they showcase forever. for more info visit here :- https://escortservicejaipur.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 84825] pages cannot properly display using book page.
https://bugs.documentfoundation.org/show_bug.cgi?id=84825 --- Comment #7 from Justin L --- *** Bug 84828 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 84828] Cannot Work Page Viewer icon
https://bugs.documentfoundation.org/show_bug.cgi?id=84828 Justin L changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #4 from Justin L --- This had been marked as a duplicate, with no indication why it was removed as a duplicate. So re-setting duplicate mode. *** This bug has been marked as a duplicate of bug 84825 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145578] The WEEKS() function gives an incorrect answer around January 4th
https://bugs.documentfoundation.org/show_bug.cgi?id=145578 Mike Kaganski changed: What|Removed |Added Keywords||difficultyBeginner, ||easyHack, skillCpp --- Comment #2 from Mike Kaganski --- (In reply to Yuri Pieters from comment #0) > Additional Info: > The operation of the function is described in the source file, which I read > at this link: > https://github.com/LibreOffice/core/blob/ > 14cfff500e93f0d6cbf8412065feea85c01ea81d/scaddins/source/datefunc/datefunc. > cxx#L442 You are completely correct, and the problem is using integral division by 7 there, which gives 0 for both first week of the year of nStartDate, as well as for the week before it. std::floor should be used instead. The easy hack should include a unit test. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145585] EDITING linked and gruped images
https://bugs.documentfoundation.org/show_bug.cgi?id=145585 Gustav Wall changed: What|Removed |Added Summary|EDITING |EDITING linked and gruped ||images -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145585] New: EDITING
https://bugs.documentfoundation.org/show_bug.cgi?id=145585 Bug ID: 145585 Summary: EDITING Product: LibreOffice Version: 6.0.7.3 release Hardware: ARM OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pend...@sprechrun.de Created attachment 176145 --> https://bugs.documentfoundation.org/attachment.cgi?id=176145=edit example linked and gruped images Hi, I have assigned links to individual images and then grouped the images - see attachment. Now I can't find a way to edit these pictures, e.g. to change the link or to ungroup them. Whether I click with the right or left mouse button, I jump to the link. What can I do to ungroup the images and edit the links? My working environment: cat /etc/os-release NAME="Ubuntu" VERSION="18.04.5 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.5 LTS" VERSION_ID="18.04" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144994] libreoffice crashes with kf5-wayland when LanguageTool extension is in use
https://bugs.documentfoundation.org/show_bug.cgi?id=144994 --- Comment #23 from Michael Weghorn --- (In reply to giors_00 from comment #22) > I really would like to contribute by testing: could you please advice me > about how to install the alpha-daily release on archlinux (only deb/rpm > package are available and debtap+pacman -u maybe is not the best way to > proceed for testing)? I used to try appimage versions, but according to > https://libreoffice.soluzioniopen.com/daily-version/, they seem to be quite > old. > > Sorry for bothering with such a (probably) silly question. Thanks a lot for your willingness to test. It's not a silly question at all, I had to think about that myself when using the Arch VM... In the end, you can use + extract the .deb packages just like on Debian or Ubuntu as described here: https://wiki.documentfoundation.org/Installing_in_parallel/Linux (I used the Debian packages and thus the 'dpkg-deb -x' commands mentioned on that page. dpkg can be installed from the arch repo just fine.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145584] New: Writer crashes on exporting as PDF with its Range in PDF Options set to 'Selection'
https://bugs.documentfoundation.org/show_bug.cgi?id=145584 Bug ID: 145584 Summary: Writer crashes on exporting as PDF with its Range in PDF Options set to 'Selection' Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: himajin100...@gmail.com Description: see steps to reproduce Steps to Reproduce: 1. Start Writer 2. [File]->[Export As]->[Export As PDF] 3. in the [PDF Options] dialog, select [General] Tab. 4. You will find [Range] section. Choose 'Selection' radio button 5. Click [Export] button to close the dialog. Actual Results: crash Expected Results: no crash Reproducible: Always User Profile Reset: No Additional Info: reproducible with Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 742b8befecbcfc0cfab87cfcd87c83b7d8ef32ab CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: ja-JP (ja_JP); UI: en-US Calc: CL non-reproducible with Version: 7.2.3.1 (x64) / LibreOffice Community Build ID: 1d5dee817bde88d78dbcc0d00f88492568e131d5 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: default; VCL: win Locale: ja-JP (ja_JP); UI: ja-JP Calc: CL --- this line may be related. https://opengrok.libreoffice.org/xref/core/vcl/win/gdi/salprn.cxx?r=a2adb7fa=44004=1105#1105 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145578] The WEEKS() function gives an incorrect answer around January 4th
https://bugs.documentfoundation.org/show_bug.cgi?id=145578 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from Mike Kaganski --- Repro. Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 12; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: ru-RU (ru_RU); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136294] Red wrong spelled lining needs a trigger to get activated (spell checker)
https://bugs.documentfoundation.org/show_bug.cgi?id=136294 Ezinne changed: What|Removed |Added CC||nipatriknils...@gmail.com --- Comment #17 from Ezinne --- *** Bug 137169 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 137169] spellchecker doesn't give immediate feedback
https://bugs.documentfoundation.org/show_bug.cgi?id=137169 Ezinne changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #4 from Ezinne --- I think this issue may be a duplicate of Bug 136294. Considering the description of this issue and conversations on Bug 136294. *** This bug has been marked as a duplicate of bug 136294 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38263] Zooming presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=38263 --- Comment #24 from Pavithra --- https://intellimindz.com/sap-abap-training-in-chennai/;>sap abap tarining In Chennai https://intellimindz.com/sap-hr-training-in-chennai/;>sap hr training In Chennai https://intellimindz.com/sap-hana-training-in-chennai/;>sap hana training In Chennai https://intellimimdz.com/sap-scm-training-in-chennai/;>sap scm training In Chennai https://intellimindz.com/sap-bo-training-in-chennai/;>sap bo training In Chennai https://intellimindz.com/sap-pp-training-in-chennai/;>sap pp training In Chennai -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38263] Zooming presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=38263 Pavithra changed: What|Removed |Added Keywords||topicWeb URL||https://intellimindz.com/sa ||p-pp-training-in-chennai/ --- Comment #23 from Pavithra --- SAP ARIBA Training in Chennai SAP ABAP Training in Chennai SAP HR Training in Chennai SAP HANA Training in Chennai SAP SCM Training in Chennai SAP BO Training in Chennai -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145292] Enhancement: Calc UI - Defaults in Find dialogue and toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=145292 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 145291] CALC evaluation of ad hoc labels fails when a CELL within the label array is included in the formula
https://bugs.documentfoundation.org/show_bug.cgi?id=145291 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 145289] Charts fail to update by dragging data selection handles
https://bugs.documentfoundation.org/show_bug.cgi?id=145289 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 145577] Crash in: xrhkbczd.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=145577 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145577] Crash in: xrhkbczd.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=145577 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141527] Crash in: SfxInfoBarWindow::addButton(PushButton*)
https://bugs.documentfoundation.org/show_bug.cgi?id=141527 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 141527] Crash in: SfxInfoBarWindow::addButton(PushButton*)
https://bugs.documentfoundation.org/show_bug.cgi?id=141527 --- Comment #6 from QA Administrators --- Dear John Brock, 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 141262] libreoffice can't generate word 2003 xml file rightliy , especial it has table in
https://bugs.documentfoundation.org/show_bug.cgi?id=141262 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 141262] libreoffice can't generate word 2003 xml file rightliy , especial it has table in
https://bugs.documentfoundation.org/show_bug.cgi?id=141262 --- Comment #3 from QA Administrators --- Dear netmou, 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 142224] Writer crashes and cannot load
https://bugs.documentfoundation.org/show_bug.cgi?id=142224 --- Comment #2 from QA Administrators --- Dear willard6, 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 142208] Bucle infinito inesperado dentro de IF...THEN...END IF al ejecutar el procedimiento mediante cualquier Suceso
https://bugs.documentfoundation.org/show_bug.cgi?id=142208 --- Comment #2 from QA Administrators --- Dear ramon6419, 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 139707] Calc loses spreadsheet rows when creating .xlsx file from .CSV file containing CR (ascii=13) character. Creating plain .xls file works properly.
https://bugs.documentfoundation.org/show_bug.cgi?id=139707 --- Comment #4 from QA Administrators --- Dear teccardt, 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 135090] Locale not set properly?
https://bugs.documentfoundation.org/show_bug.cgi?id=135090 --- Comment #10 from QA Administrators --- Dear Seán Ó Séaghdha, 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 99883] Chart axis description is not imported properply
https://bugs.documentfoundation.org/show_bug.cgi?id=99883 --- Comment #11 from QA Administrators --- Dear Dennis Roczek, 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 92502] FORMATTING: Writer for Linux text height mismatch with Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=92502 --- Comment #23 from QA Administrators --- Dear mozello, 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 45028] label of connector, ordinary lines and arrow gets written through line
https://bugs.documentfoundation.org/show_bug.cgi?id=45028 --- Comment #40 from QA Administrators --- Dear hdv.jadev, 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 128650] Calling setToDefault doesn't work in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=128650 --- Comment #3 from QA Administrators --- Dear Mark Hung, 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 127995] Lines and line ends: Different arrow size left/right
https://bugs.documentfoundation.org/show_bug.cgi?id=127995 --- Comment #4 from QA Administrators --- Dear Florian, 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 121219] UI: Split view separator lines responsive on double click only after move by mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=121219 --- Comment #4 from QA Administrators --- Dear Thomas Lendo, 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 113601] Starting soffice --invisible is not entirely invisible on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=113601 --- Comment #5 from QA Administrators --- Dear Loic Nageleisen, 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 145583] [Mac OS X] Kerning is poor and haphazard
https://bugs.documentfoundation.org/show_bug.cgi?id=145583 kald...@gmail.com changed: What|Removed |Added Summary|[Mac OS X] Bad kerning |[Mac OS X] Kerning is poor ||and haphazard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145583] [Mac OS X] Bad kerning
https://bugs.documentfoundation.org/show_bug.cgi?id=145583 --- Comment #1 from kald...@gmail.com --- Created attachment 176143 --> https://bugs.documentfoundation.org/attachment.cgi?id=176143=edit Comparison of LibreOffice kerning with TextEdit Kerning problems are highlighted in red. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145583] New: [Mac OS X] Bad kerning
https://bugs.documentfoundation.org/show_bug.cgi?id=145583 Bug ID: 145583 Summary: [Mac OS X] Bad kerning Product: LibreOffice Version: 7.1.6.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: graphics stack Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kald...@gmail.com Description: Kerning in LibreOffice seems to be quite haphazard. This is more noticeable with some fonts than others. In the screenshot I've attached, the font is Cambria (12 pt). Obvious kerning problems are highlighted in red. In this case, kerning is worse with "pair kerning" on. However, if I switch the font to Arial, all the obvious kerning problems are in the version with "pair kerning" off. Note especially that the kerning is inconsistent for the same letter pairs and words. I've never seem any other MacOS program exhibit these kerning problems (likely because they let the OS handle the text display). The screenshot shows kerning in the TextEdit program for comparison. Reports of this issue seem to date back almost 10 years. Regardless, the closest pre-existing bug I could find was Bug 87373 which was closed as fixed (mainly because the bug had become too long and unwieldy). Steps to Reproduce: 1. Choose a non-monospace font (Arial for example). 2. Type some text. Actual Results: The kerning is haphazard. Even if you type the same word twice, it will have completely different kerning the second time. Expected Results: The kerning is clean and consistent (as you see in other MacOS programs). Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.6.2 / LibreOffice Community Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3 CPU threads: 4; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-US (en_UZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140290] Make "Column" (or Row) a static label for quick access per keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=140290 --- Comment #7 from fender --- >Why don't u guys reinvent the column sorting altogether. Why don't you make it >sortable by simple text. Instead of doing it the old GUI way, just give the >users a text field with CSV-type of separation. I obviously mean via column letters here, not labels. What you do with the labels is your guyses prerogative. I personally never use labels. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140290] Make "Column" (or Row) a static label for quick access per keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=140290 fender changed: What|Removed |Added CC||n4lph4-mozi...@yahoo.com --- Comment #6 from fender --- Hello Heiko Tietze. thanks for trying to implement this and advocating for it. I think I have a way to make all camps happy. The ones that want to be grammatically consistent, even though I see nothing wrong here, save work for the ones that "have to" code around the 'Column A' issue and so on. Why don't u guys reinvent the column sorting altogether. Why don't you make it sortable by simple text. Instead of doing it the old GUI way, just give the users a text field with CSV-type of separation. Take this short video as example. (mute for audio. I always forget to remove it) Once I sort, I have to go through the whole process again, unless I make a macro at which point I might as well just have a text field for sorting. https://vimeo.com/643321746 Now, some people might have the spatial foresight knowing how they will want to sort their columns to best fit their reading in relation to what they want to extract information-wise, but I'm certain the majority doesn't know until they start sorting. That way folks like me, keyboard folks, don't need to use the GUI at all. I would still prefer for it to be letter first, for the adhoc quick sorting, but that's meeting half-way. It won't be as clean as only having to use the left hand because I will have to lift my hand off the mouse to input the comma, but it'll be manageable. Less work to implement bc no hacks needed and way easier to sort for almost everyone. And hacking around it will be the biggest easter egg ever since it's completely unintuitive. not even the laziest keyboard users will think of using the letter if the letter isn't the first thing the line has. Unless it happens accidentally or they read it in a guide. One of the reasons the firefox folks didn't want to implement it actually https://bugzilla.mozilla.org/show_bug.cgi?id=1701324 giving users an option to save their sort in GUI with a tickbox 'remember sort' would be great too. It seems not even google has thought of that. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133870] Page wrap and anchoring changes copy/paste using Windows clipboard (since 6.4)
https://bugs.documentfoundation.org/show_bug.cgi?id=133870 --- Comment #4 from Aron Budea --- Interestingly regular RTF paste doesn't even copy the shape. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142279] DIGITAL SIGNATURE: Can't start certificate manager in Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=142279 Juan Jose Pablos changed: What|Removed |Added Summary|DIGITAL SIGNATURE: Can't|DIGITAL SIGNATURE: Can't |start certifcate manager in |start certificate manager |Linux |in Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145575] Calc opening ods very slowly
https://bugs.documentfoundation.org/show_bug.cgi?id=145575 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #5 from m.a.riosv --- Instant for me: Version: 7.2.3.1 (x64) / LibreOffice Community Build ID: 1d5dee817bde88d78dbcc0d00f88492568e131d5 CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134293] Inconsistent double-click AutoFill behavior
https://bugs.documentfoundation.org/show_bug.cgi?id=134293 Dmitry T. changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134293] Inconsistent double-click AutoFill behavior
https://bugs.documentfoundation.org/show_bug.cgi?id=134293 --- Comment #10 from Dmitry T. --- @Buovjaga Oops, was planning to respond, but it slipped my mind at some point, sorry. Just checked on LO 7.1.6.2, the test case file gives me the same result as in comment #1. I also had a chance to check out behavior of AutoFill in Excel 2019 (build 2110), turns out it's not affected by hidden rows at all. If we go by comment #1's steps, at step 3 AutoFill will set cells B11/B14 and stop, and at step 5 it will set both B18 and B19, and stop. In LO, on the other hand, AutoFill does not set hidden cells. Actually, turns out there is also a problem with manually filling cells by dragging the handle across the hidden row - in Excel it sets hidden cells, but in LO they remain unchanged. So, the question we first need to answer is, which behavior is actually expected - should hidden cells be filled (as they do in Excel), considered a stop (as cells B11/B14 do in LO) or ignored completely (as cells B18 and B19 do in LO (but in such case AutoFill should honor the neighboring columns))? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133811] The program does not continue with 'Dim' or 'ReDim' following 'If' in one line statement.
https://bugs.documentfoundation.org/show_bug.cgi?id=133811 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5570 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145570] ReDim spills out of scope
https://bugs.documentfoundation.org/show_bug.cgi?id=145570 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||3811 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 45034] Presenter Console: no scrolling with mouse wheel in slide overview possible
https://bugs.documentfoundation.org/show_bug.cgi?id=45034 --- Comment #14 from Tedo Vrbanec --- One can not scroll with a mouse wheel in the notes box but must use sliding next to the text notes during the presentation with the presentation console. Useful when it is a bit more text that does not fit in the box. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145570] ReDim spills out of scope
https://bugs.documentfoundation.org/show_bug.cgi?id=145570 --- Comment #3 from himajin100...@gmail.com --- just a guess: Sub Main() Dim X() As Integer A: Redim X(1) Goto C: ' Probably While runtime gotes to C, Parser goes to B, not C. B: X(1,1) = 3 Exit Sub C: Redim X(1,1) Goto B: End Sub -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144985] Chart custom colors are not used in the legend
https://bugs.documentfoundation.org/show_bug.cgi?id=144985 --- Comment #7 from himajin100...@gmail.com --- Oops, posted on wrong report. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144985] Chart custom colors are not used in the legend
https://bugs.documentfoundation.org/show_bug.cgi?id=144985 --- Comment #6 from himajin100...@gmail.com --- Sub Main() Dim X() As Integer A: Redim X(1) Goto C: ' Probably While runtime gotes to C, Parser goes to B, not C. B: X(1,1) = 3 Exit Sub C: Redim X(1,1) Goto B: End Sub -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145322] Writer: All characters rotate when printing a vertical writing page
https://bugs.documentfoundation.org/show_bug.cgi?id=145322 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4378 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144378] Calc: Characters rotated when printed in Asian layout mode of vertical writing
https://bugs.documentfoundation.org/show_bug.cgi?id=144378 himajin100...@gmail.com changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5322 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145570] ReDim spills out of scope
https://bugs.documentfoundation.org/show_bug.cgi?id=145570 --- Comment #2 from himajin100...@gmail.com --- and similar fix may be needed for single-line redim and for other branching syntax such as Switch-case. Another thing I'm just a bit concerned is "Go To" Statement. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145570] ReDim spills out of scope
https://bugs.documentfoundation.org/show_bug.cgi?id=145570 --- Comment #1 from himajin100...@gmail.com --- just a guess: should we prepare stack-thingy that holds dimensions for each block , pop and reset to that dimensions here https://opengrok.libreoffice.org/xref/core/basic/source/comp/loops.cxx?r=ab9b67bb#63 and before Parse() here? https://opengrok.libreoffice.org/xref/core/basic/source/comp/loops.cxx?r=ab9b67bb#74 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144867] Regression: Font size selector rounds current configuration to integer in Font property dialogs
https://bugs.documentfoundation.org/show_bug.cgi?id=144867 --- Comment #5 from Callegar --- Issue is still present in 7.2.3.1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145258] Comments cut-off in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=145258 Caolán McNamara changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | Keywords|bibisectRequest | Status|NEW |ASSIGNED --- Comment #17 from Caolán McNamara --- While I was initially fixated on the multiline widget I think the problem is actually with the calculation of the height of the author/date fields -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145577] Crash in: xrhkbczd.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=145577 --- Comment #5 from Alx --- Thanks! Running version 201303011342 which is the latest available for win10 x64 from support.xerox.com Tried to remove printer software and drivers including all threads in registry, before rebooting and re-installing printer software and drivers in one pc. However, at least two pc's (one desktop and one laptop) are affected. Both are running Libre office (and win10) Both are using USB to connect. As pdf's can be printed (and printer setup/testpage) I think it's connected to the virtual (usb) printer port somehow. Br, -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144923] Version 7.2 Impress, Slide advance not working in full screen
https://bugs.documentfoundation.org/show_bug.cgi?id=144923 --- Comment #15 from abal...@gmail.com --- Created attachment 176142 --> https://bugs.documentfoundation.org/attachment.cgi?id=176142=edit With Force software option enabled Another data point for you. I selected the "Force Skia software rendering" option as well and tested slide-mode and it worked as expected in that configuration as well. I hope that helps. To summarize, Working configurations: Force Skia software rendering Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Skia disabled Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Non-working config: Skia enabled Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Windows 10.0 Build 19043; 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 144923] Version 7.2 Impress, Slide advance not working in full screen
https://bugs.documentfoundation.org/show_bug.cgi?id=144923 --- Comment #14 from abal...@gmail.com --- Created attachment 176141 --> https://bugs.documentfoundation.org/attachment.cgi?id=176141=edit Attached file as requested. Here you go. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145581] Writer - Change in font effect (UPPERCASE) in Heading Style does not get reflected in the Index-TOC
https://bugs.documentfoundation.org/show_bug.cgi?id=145581 --- Comment #2 from phv --- "Table of Contents" has its own style that can be set via the "Styles" tab of the "Table of Content, Index, or Bibliography" menu. I find no logic in the suggestion that the ToC should keep by default the character or paragraph style of the entries (font, font effects, etc.). These are different and independent elements on a document. Moreover, you can write the titles in upper case and the letter case will be applied directly in the table of contents. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145577] Crash in: xrhkbczd.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=145577 --- Comment #4 from Buovjaga --- Looking at the other report associated with this crash signature, bug 128989, the user had a Xerox Phaser and indeed, a web search tells that xrhkbczd.dll is for Xerox Phasers. Alx: the reporter in bug 128989 said that the problem was resolved with new firmware. Can you look into it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144923] Version 7.2 Impress, Slide advance not working in full screen
https://bugs.documentfoundation.org/show_bug.cgi?id=144923 Buovjaga changed: What|Removed |Added Summary|Version 7.2 Impress, Slide |Version 7.2 Impress, Slide |advance not working in full |advance not working in full |screen with Skia|screen --- Comment #13 from Buovjaga --- (In reply to abalsam from comment #11) > I can confirm that when I deactivated Skia, things worked as they should. > My question is would it still be useful to do the requested bibisect or > since there is now an identified workaround it is no longer required? Even though this is not what the original report was about, I guess you could attach this file to the report: C:\Users\User\AppData\Roaming\LibreOffice\4\cache\skia.log -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145579] fake bug
https://bugs.documentfoundation.org/show_bug.cgi?id=145579 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID Component|LibreOffice |deletionRequest --- Comment #1 from Buovjaga --- Enjoy your ban, I hope it's worth it for the lab work -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 40027] Data point symbols are wrong in import Excel xls-files
https://bugs.documentfoundation.org/show_bug.cgi?id=40027 --- Comment #13 from himajin100...@gmail.com --- haven't investigated yet, but possibly related? https://opengrok.libreoffice.org/xref/core/oox/source/drawingml/chart/seriesconverter.cxx?r=3c1085fc#872 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145577] Crash in: xrhkbczd.dll
https://bugs.documentfoundation.org/show_bug.cgi?id=145577 --- Comment #3 from Alx --- Since this has been an issue for the latest year or so, I find it hard to believe that it would be solved by now. Please investigate further. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145581] Writer - Change in font effect (UPPERCASE) in Heading Style does not get reflected in the Index-TOC
https://bugs.documentfoundation.org/show_bug.cgi?id=145581 --- Comment #1 from Paco --- Created attachment 176140 --> https://bugs.documentfoundation.org/attachment.cgi?id=176140=edit Link to short (80'') video showing the process -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145582] New: FILEOPEN FILESAVE SQL file for editing/saving treats file as changed when no changes have occurred
https://bugs.documentfoundation.org/show_bug.cgi?id=145582 Bug ID: 145582 Summary: FILEOPEN FILESAVE SQL file for editing/saving treats file as changed when no changes have occurred Product: LibreOffice Version: 7.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: barryorie...@gmail.com Description: When I open an SQL file in BASE, the file is already marked a "changed" when I haven't made any changes. This forces me to respond to the SAVE dialog when I close the unedited file. Not a showstopper by any means but annoying nonetheless. This doesn't happen in CALC or WRITE. Steps to Reproduce: 1. Open any SQL file Edit/Edit in SQL Mode 2. The SAVE icon has a red dot indicating the file has been changed when it hasn't 3. Close the unedited file Actual Results: Closing the unedited SQL file cause the File Save dialog to pop up. Expected Results: Upon opening, the SQL file should not be considered "changed" when no changes have occurred. The File Save dialog should not pop up when closing an unedited file. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 6; OS: Windows 10.0 Build 22000; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145581] New: Writer - Change in font effect (UPPERCASE) in Heading Style does not get reflected in the Index-TOC
https://bugs.documentfoundation.org/show_bug.cgi?id=145581 Bug ID: 145581 Summary: Writer - Change in font effect (UPPERCASE) in Heading Style does not get reflected in the Index-TOC Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: paco.cruz.iesbe...@gmail.com Description: The change in Heading style->Font Effect->UPPERCASE does not propagate to the index|Table of Content, after updating it. Steps to Reproduce: 1. Create a new doc, new paragraph and apply a Heading (any heading) paragraph style. 2. Insert a TOC 2. Change the Heading style Font Effects->Effects->UPPERCASE, apply. The Heading is displayed in UPPERCASE 3. Update TOC 4. The TOC does not reflect the paragraph entry in UPPERCASE Actual Results: The TOC does not reflect the change of case (UPPERCASE) in the heading style. Expected Results: IMHO, the TOC should reflect the "actual case" (UPPERCASE) of the paragraph entry. If I type a TOC entry in an ALL UPPERCASE, or in a mixed case, the TOC shows its case OK. But the change in the heading style is not propagated to the TOC. Reproducible: Always User Profile Reset: No Additional Info: I really doesn't know for sure if this has to be considered a "real" bug, or a matter of formatting style of the TOC. Please ignore this report if what I am saying does not make sense :-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145282] Group of objects doesn't retain its position when page is moved up
https://bugs.documentfoundation.org/show_bug.cgi?id=145282 --- Comment #2 from phv --- Note also that this bug, still present in the last LibreOffice dev version, ignores that the vertical position of the group of objects is protected and modifies it so that the group is moved as low as possible on the page even if it means covering the margin (the group is in foreground and doesn't allow overlap). The regression is likely to ruin page layouts if this version is made available more widely to the public. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 40027] Data point symbols are wrong in import Excel xls-files
https://bugs.documentfoundation.org/show_bug.cgi?id=40027 --- Comment #12 from himajin100...@gmail.com --- Memo: when c:varyColors exists, colors seem to be taken from accent colors in theme.xml -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145386] bogus lang-tag in status bar language selector
https://bugs.documentfoundation.org/show_bug.cgi?id=145386
Eike Rathke changed:
What|Removed |Added
Assignee|libreoffice-b...@lists.free |er...@redhat.com
|desktop.org |
Status|NEW |ASSIGNED
--- Comment #1 from Eike Rathke ---
So I dug deeper into this than anticipated.. Writer has no handling of the LCID
0x0400 LANGUAGE_PROCESS_OR_USER_DEFAULT language/locale concept, in fact it
also explicitly doesn't expect our LANGUAGE_SYSTEM locale assigned as character
attribution. The status bar is just a cosmetic symptom, the same "{en-GB}" or
in 7.3 "English (United Kingdom) {en-GB}" string is displayed in the status bar
menu and in the character/paragraph font attribution language list, worse, it
appears in both Western and CJK lists.
Coming up with a tentative fix for the language/locale display.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145575] Calc opening ods very slowly
https://bugs.documentfoundation.org/show_bug.cgi?id=145575 --- Comment #4 from Jens Peper --- Created attachment 176139 --> https://bugs.documentfoundation.org/attachment.cgi?id=176139=edit Simple test file in ods format Simple file created by calc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145575] Calc opening ods very slowly
https://bugs.documentfoundation.org/show_bug.cgi?id=145575 --- Comment #3 from Jens Peper --- This is different Bug 143926 as calc is running fine but opening an ods takes ages. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141573] CALC Sort Issue
https://bugs.documentfoundation.org/show_bug.cgi?id=141573 Joseph Conner changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO|RESOLVED --- Comment #4 from Joseph Conner --- After upgrading to the latest Ubuntu 21.10 I no longer have this problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145571] LibreOffice Clac: on a big file deleting multiple rows (using ctrl+click) is significantly slower than deleting the same rows one-by-one
https://bugs.documentfoundation.org/show_bug.cgi?id=145571 --- Comment #1 from Timur --- Please attach sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145580] New: Comment balloon doesn't allow Latin characters
https://bugs.documentfoundation.org/show_bug.cgi?id=145580 Bug ID: 145580 Summary: Comment balloon doesn't allow Latin characters Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hildo...@gmail.com Comment balloon doesn't allow Latin characters as ã, é, à, ... I am using the LibreOffice Writer 7.2.2 build 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 on Ubuntu 20.04. The OS and LibreOffice installation are default English language, but I have installed the Portuguese language spelling. The document text works fine, recognize spelling Portuguese/English typing and allow me any character of my keyboard or combinations ñ (for Spanish), ã, é, à (large used on Portuguese). The issue is on the comment balloons of revisions tools, it doesn't recognize this characters. Workflow: to type ã, I have to first type ~ and after a on my keyboard. On text works fine but on the balloons only type "a" after this combination. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145575] Calc opening ods very slowly
https://bugs.documentfoundation.org/show_bug.cgi?id=145575 --- Comment #2 from Timur --- Please attach sample file. Seems duplicate of Bug 143926. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145579] New: fake bug
https://bugs.documentfoundation.org/show_bug.cgi?id=145579 Bug ID: 145579 Summary: fake bug Product: LibreOffice Version: unspecified Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: honamo6...@epeva.com Please mark this as a fake bug, I need to do this for my lab work :( -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144923] Version 7.2 Impress, Slide advance not working in full screen with Skia
https://bugs.documentfoundation.org/show_bug.cgi?id=144923 Timur changed: What|Removed |Added Summary|Version 7.2 Impress, Slide |Version 7.2 Impress, Slide |advance not working in full |advance not working in full |screen |screen with Skia --- Comment #12 from Timur --- This is not WFM but New Skia bug where bibisect would be welcome. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145578] New: The WEEKS() function gives an incorrect answer around January 4th
https://bugs.documentfoundation.org/show_bug.cgi?id=145578
Bug ID: 145578
Summary: The WEEKS() function gives an incorrect answer around
January 4th
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: magejohny...@gmail.com
Description:
The WEEKS function appears to be giving an incorrect answer when calculating a
calendar week difference before January 4th of a year.
I've tried to work through the calculation as given in the source code
separately, and when I did this I got the correct answer, so I'm not sure where
the issue could be coming from.
Steps to Reproduce:
1. Put "=WEEKS("2022-01-09","2022-01-10",1)" in a cell
2. Put "=WEEKS("2022-01-02","2022-01-03",1)" in a second cell
I found another set of dates that illustrate the problem too:
"=WEEKS("2017-01-08","2017-01-09",1)"
"=WEEKS("2017-01-01","2017-01-02",1)"
Actual Results:
The first cell shows 1, the second one shows 0.
Expected Results:
Both cells should have shown 1.
Reproducible: Always
User Profile Reset: Yes
OpenGL enabled: Yes
Additional Info:
The operation of the function is described in the source file, which I read at
this link:
https://github.com/LibreOffice/core/blob/14cfff500e93f0d6cbf8412065feea85c01ea81d/scaddins/source/datefunc/datefunc.cxx#L442
--
You are receiving this mail because:
You are the assignee for the bug.
