[Libreoffice-bugs] [Bug 153058] Android Viewer: Allow zooming out to see full page in landscape orientation
https://bugs.documentfoundation.org/show_bug.cgi?id=153058 Michael Weghorn changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153058] Android Viewer: Allow zooming out to see full page in landscape orientation
https://bugs.documentfoundation.org/show_bug.cgi?id=153058 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- Created attachment 184705 --> https://bugs.documentfoundation.org/attachment.cgi?id=184705=edit Screencast with pending Gerrit changes in place Pending Gerrit changes: https://gerrit.libreoffice.org/c/core/+/145657 https://gerrit.libreoffice.org/c/core/+/145658 Attached is a screencast of the behaviour with the changes in place. For double-tap, adapting zoom level to the page width is still used, rather than the new minimum zoom level, because it IMHO fits better for using the app on smaller devices, s. commit message for details. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153047] PDF Export: default text in content control is gone
https://bugs.documentfoundation.org/show_bug.cgi?id=153047 Miklos Vajna changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #2 from Miklos Vajna --- I believe this is an intentional change. We used to export content controls as plain text, and now we export them as PDF form widgets if the "create pdf forms" option of the PDF export is enabled. That option happens to be on by default. Is there something I can fix here without breaking the use-case where you can insert content controls to a Writer document, export it as PDF and you get a fillable form, similar to what also works with control shapes? Should we disable "create pdf forms" by default? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153058] New: Android Viewer: Allow zooming out to see full page in landscape orientation
https://bugs.documentfoundation.org/show_bug.cgi?id=153058 Bug ID: 153058 Summary: Android Viewer: Allow zooming out to see full page in landscape orientation Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: Android Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Android Viewer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: m.wegh...@posteo.de Created attachment 184704 --> https://bugs.documentfoundation.org/attachment.cgi?id=184704=edit Screencast of current behavior [I received this request from a user by email, reporting it here for further processing.] Android Viewer has a minimum zoom level so that zooming out further than making the page width fill the screen width doesn't work (results in auto-zooming back to that level). This makes it impossible to see a full portrait page when the device is used in landscape orientation, s. attached screencast. Steps to reproduce: 1) switch Android device to landscape mode 2) open a Writer document in page format A4, portrait 3) zoom out to see the full page Actual result: Auto-zoom back in happens so that it's impossible to see the whole page at once. Desired result: No auto-zoom or auto-zoom only to the point where the whole page is still visible. Version: 7.6.0.0.alpha0+ Build ID: 9c87fe9eff2c -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 91265] MSO2013 Template - D Business Verification - Chart Size Too Large
https://bugs.documentfoundation.org/show_bug.cgi?id=91265 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152661] "Hybrid PDF" must share embedded media between the ODT and the proper PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=152661 --- Comment #9 from Tomaz Vajngerl --- Thinking a bit about it I don't think this is that hard to implement. We don't really need to mess with the PDF structure - all we really need is to extract all the images from the PDF (easily done with PDFium I think), make sure to preserve the image name (various solutions) and reconstruct the ODF document before reading in the filter, then normally open the document. When saving the hybrid PDF, we save the ODF normally, but just skip saving the images. There are some issues like making sure we don't re-compress the images when saving them to PDF (disable that option with hybrid PDF) and that the images are all compatible, if not we would duplicate them or something else. This probably wouldn't work for fonts as PDF subsets the fonts, and normally the fonts also aren't included into ODF. For a max compatibility option we could however embed the whole font into PDF and do a similar thing like with images also for fonts. I like this idea, because smaller the overhead of hybrid PDF the more likely it is the user will use it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153057] Calc and Base can not filter time values
https://bugs.documentfoundation.org/show_bug.cgi?id=153057 --- Comment #2 from Andreas Säger --- Created attachment 184703 --> https://bugs.documentfoundation.org/attachment.cgi?id=184703=edit Spreadsheet with list range menu:Data>filter>Standard filter... Works with a selected time Fails with entered time or with operator other than = -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153057] Calc and Base can not filter time values
https://bugs.documentfoundation.org/show_bug.cgi?id=153057 --- Comment #1 from Andreas Säger --- Created attachment 184702 --> https://bugs.documentfoundation.org/attachment.cgi?id=184702=edit database document with 2 forms Test the form/subform filtering and the built-in filters. Everything works properly unless you filter by time values in "Duration". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153055] [FILESAVE] Wrong parsening of CSV file
https://bugs.documentfoundation.org/show_bug.cgi?id=153055 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #1 from Mike Kaganski --- This is not a bug. (In reply to eduardomozart182 from comment #0) > I'd imported a CSV file to LibreOffice with the following line: > > "MSSQL 2017 - Qualitor - Usuário ""qualitor""","R > Networks",Teampass,,qualitor,Qualitor!@#,"Usu?rio interno da inst?ncia > \"MSSQLSERVER\" do MSSQL 2017 (server02), utilizado para conex?o da > aplica??o Qualitor Web ao banco de dados do Qualitor. Para autentica??o ao > banco de dados do Qualitor, ? necess?rio usar os usu?rios de dom?nio > \"eduardo.mozart\", \"roberto.oliveira\" ou \"Administrator\"." > > > Steps to Reproduce: > 1. I opened it with LibreOffice only with the "Separated by" 'Comma' > selected. It loads and shows up into the right columns as expected. No, it doesn't load "as expected", because if you inspect it carefully, the following piece goes into column H (i.e., into the next cell): \"roberto.oliveira\" ou \"Administrator\"." and the cell in column G ends with \"eduardo.mozart\ And this is the correct behavior. If you look at the first field in the CSV, it looks like "MSSQL 2017 - Qualitor - Usuário ""qualitor""" and appears in Calc as MSSQL 2017 - Qualitor - Usuário "qualitor" The quotations work as expected, according to the CSV specification RFC 4180 [1]: > 7. If double-quotes are used to enclose fields, then a double-quote > appearing inside a field must be escaped by preceding it with > another double quote. For example: > > "aaa","b""bb","ccc" Note: to escape the double-quote character, you use *another double-quote character*! Now look at the 7th field (as one *could* expect): "Usu?rio interno da inst?ncia \"MSSQLSERVER\" do MSSQL 2017 (server02), utilizado para conex?o da aplica??o Qualitor Web ao banco de dados do Qualitor. Para autentica??o ao banco de dados do Qualitor, ? necess?rio usar os usu?rios de dom?nio \"eduardo.mozart\", \"roberto.oliveira\" ou \"Administrator\"." It starts and ends with a double-quote; and all internal double-quotes *must* be escaped using another double-quote. But they are not. Instead, backslash is used for that - which is wrong. And when parsing such a field, Calc finds an *unescaped* double-quote, immediately followed by proper field delimiter (comma), which happens after eduardo.mozart\; Calc correctly ends the field here, and starts another field - which gets the rest. And then, it outputs this to the file according to your specifications; the field delimiter changes to semicolon, and it's used to separate 7th and 8th fields. [1] https://www.rfc-editor.org/rfc/rfc4180 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153057] New: Calc and Base can not filter time values
https://bugs.documentfoundation.org/show_bug.cgi?id=153057 Bug ID: 153057 Summary: Calc and Base can not filter time values Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ville...@t-online.de Description: Calc's standard filter dialog displays the existing time values as formatted in the respective column. If you choose any of the values with operator =, the filter result is OK. In the attached song list, there are 4 songs with a lenght of 00:01:58. When you change the operator or when you manually enter some time value, the filter always fails with no resulting records. "Advanced filtering" works well. The problem affects both forms of the attached database. The form reports an error and the form document needs to be reloaded in order to be usable again. I could reproduce the problem with both types of embedded databases. Steps to Reproduce: 1. Open spreadsheet and test the standard filter with some value in the "Duration" column. 2. Open the database and test filtering by time values in the "Duration" column. 3. Actual Results: 1. fails in most cases with no records 2. always fails with no records, error message and unusable form. Expected Results: Properly filtered record sets Reproducible: Always User Profile Reset: No Additional Info: none -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152923] Column and row headings in Calc lost their colored, slightly 3D look
https://bugs.documentfoundation.org/show_bug.cgi?id=152923 Heiko Tietze changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||7508 Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #5 from Heiko Tietze --- Indeed it was a deliberate decision for bug 127508. The world has become flat (design-wise 3D-effects like this add noise and make the UI unnecessarily busy). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97362] Convert Java complex tests to Python
https://bugs.documentfoundation.org/show_bug.cgi?id=97362 --- Comment #42 from Commit Notification --- Chenxiong Qi committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/be7f3df701e4d94b64af6626d53e03d9336a09cf tdf#97362 Convert unotools tempfile tests to Python It will be available in 7.6.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 97362] Convert Java complex tests to Python
https://bugs.documentfoundation.org/show_bug.cgi?id=97362 Commit Notification changed: What|Removed |Added Whiteboard| target:5.2.0 target:5.5.0 | target:5.2.0 target:5.5.0 |target:6.0.0 target:6.1.0 |target:6.0.0 target:6.1.0 |reviewed:2022 |reviewed:2022 target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153056] New: In Writer, when I modify the size of a table, Bold effect in the table disappear.
https://bugs.documentfoundation.org/show_bug.cgi?id=153056 Bug ID: 153056 Summary: In Writer, when I modify the size of a table, Bold effect in the table disappear. Product: LibreOffice Version: 7.4.2.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: doms...@yahoo.fr Description: If I modify the size of the table: for example, I add a row. The boldness of the text in the table disappear! I wanted the boldness! Steps to Reproduce: 1. I open Writer. 2. I add a table. 3. I add text in the table. 4. I bold the text in the table. 5. I modify the size of the table: for example, I add a row. Actual Results: The boldness of the text in the table disappear! Expected Results: I wanted the boldness! Reproducible: Always User Profile Reset: No Additional Info: Hello. I have: Lubuntu 22.10 64 bits. No other problem. Stable computer. Thanks. Version: 7.4.2.3 / LibreOffice Community Build ID: 40(Build:3) CPU threads: 2; OS: Linux 5.19; UI render: default; VCL: qt5 (cairo+xcb) Locale: fr-FR (fr_FR.UTF-8); UI: en-US Ubuntu package version: 1:7.4.2~rc3-0ubuntu1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152959] Find and Replace can't use the lowercase Unicode literal for soft hyphen
https://bugs.documentfoundation.org/show_bug.cgi?id=152959 Stéphane Guillou (stragu) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |stephane.guillou@libreoffic |desktop.org |e.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153055] New: [FILESAVE] Wrong parsening of CSV file
https://bugs.documentfoundation.org/show_bug.cgi?id=153055
Bug ID: 153055
Summary: [FILESAVE] Wrong parsening of CSV file
Product: LibreOffice
Version: 7.4.4.2 release
Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: eduardomozart...@gmail.com
Description:
Hello LibreOffice team!
I'd imported a CSV file to LibreOffice with the following line:
"MSSQL 2017 - Qualitor - Usuário ""qualitor""","R
Networks",Teampass,,qualitor,Qualitor!@#,"Usu?rio interno da inst?ncia
\"MSSQLSERVER\" do MSSQL 2017 (server02), utilizado para conex?o da aplica??o
Qualitor Web ao banco de dados do Qualitor. Para autentica??o ao banco de dados
do Qualitor, ? necess?rio usar os usu?rios de dom?nio \"eduardo.mozart\",
\"roberto.oliveira\" ou \"Administrator\"."
Steps to Reproduce:
1. I opened it with LibreOffice only with the "Separated by" 'Comma' selected.
It loads and shows up into the right columns as expected.
2. I select all cells and change the cell formating to "Text".
3. Go to File > Save as.
4. Selected "Text CSV" and enabled the checkbox to customize the CSV filter and
I had setup the following settings:
Field delimiter: ;
Text delimiter: "
Quote all text cells: checked
Actual Results:
When exporting, the quotes next to "eduardo.mozart" was broken. It seems that
the CSV filter didn't found the opening quote to filter it as expected and the
following output was generated:
"MSSQL 2017 - Qualitor - Usu?rio ""qualitor""";"R
Networks";"Teampass";;"qualitor";"Qualitor!@#";"Usu?rio interno da inst?ncia
\""MSSQLSERVER\"" do MSSQL 2017 (server02), utilizado para conex?o da aplica??o
Qualitor Web ao banco de dados do Qualitor. Para autentica??o ao banco de dados
do Qualitor, ? necess?rio usar os usu?rios de dom?nio \""eduardo.mozart\";"
\""roberto.oliveira\"" ou \""Administrator\"".""";
Please notice that there's a missing quote next to "eduardo.mozart" and it
added a ";" at the wrong position, breaking the CSV file and make it impossible
for our application to import it because the number of columns was wrong.
Expected Results:
I had to manually fix the file by appending one more quote and replacing the
";" character to ",":
"MSSQL 2017 - Qualitor - Usu?rio ""qualitor""";"R
Networks";"Teampass";;"qualitor";"Qualitor!@#";"Usu?rio interno da inst?ncia
\""MSSQLSERVER\"" do MSSQL 2017 (server02), utilizado para conex?o da aplica??o
Qualitor Web ao banco de dados do Qualitor. Para autentica??o ao banco de dados
do Qualitor, ? necess?rio usar os usu?rios de dom?nio \""eduardo.mozart\"",
\""roberto.oliveira\"" ou \""Administrator\"".""";
Reproducible: Always
User Profile Reset: No
Additional Info:
I'm not sure if it's a bug, but my original file had 7 columns. When exporting
it to CSV using LibreOffice, it added an extra ";" at the end of the line,
effectively creating an extra column (the output from LibreOffice created a 8
columns CSV file). I had to remove this extra column (";" from the end of each
line) manually after export because our application supports only CSV file
lines with 7 columns.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152654] Introduce List Styles in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152654 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 152841] FILEOPEN RTF/DOCX Paragraph height is defined by hidden characters even in Print mode
https://bugs.documentfoundation.org/show_bug.cgi?id=152841 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 152848] When using accents in a table (spanish), a cell break occurs.
https://bugs.documentfoundation.org/show_bug.cgi?id=152848 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 152844] Footnote separator alignment + Footnote paragraph direction flip in LO->MSO->LO round-trip
https://bugs.documentfoundation.org/show_bug.cgi?id=152844 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 152834] Track changes sets modified flag, but undo not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=152834 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 152825] Tools - Address Book Source: warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152825 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 152846] LibreOffice Writer Settings - Unnecessary unwanted white rectangular area behind list menus /w arrows (kf5)
https://bugs.documentfoundation.org/show_bug.cgi?id=152846 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 152827] Distance between symbol and index adjustable
https://bugs.documentfoundation.org/show_bug.cgi?id=152827 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 152824] Tools - Bibliography Database: warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152824 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 152816] Form - Label in a new document: warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152816 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 152823] Tools - Mail Merge Wizard: warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152823 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 152821] Tools - Line Numbering in a new document: warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152821 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 152822] Tools - Footnotes and Endnotes: warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152822 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 152820] Tools - Redact in a new document: warnings in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152820 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 152817] Tools - Spelling in a new document: warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152817 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 96209] "Impress" template is broken with "Centered Text" layout (comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=96209 --- Comment #13 from QA Administrators --- Dear Yan Pas, 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 152819] Tools - Autotext in a new document: warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152819 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 152804] Numbers in a cell equal to or greater than 10 are set to 0 upon saving and re-opening
https://bugs.documentfoundation.org/show_bug.cgi?id=152804 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 152815] Table - Split cells in a table in a new document: warning in console with debug LO
https://bugs.documentfoundation.org/show_bug.cgi?id=152815 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 149981] Footer Page numbers with endnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=149981 --- Comment #2 from QA Administrators --- Dear Ian Jarvis, 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 93123] VIEWING: Split/frozen sheet not redrawn properly when formula with manual range selection causes page to scroll
https://bugs.documentfoundation.org/show_bug.cgi?id=93123 --- Comment #16 from QA Administrators --- Dear tmacalp, 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 88678] Writer: slow screen rendering with certain documents/zoom levels
https://bugs.documentfoundation.org/show_bug.cgi?id=88678 --- Comment #12 from QA Administrators --- Dear crxssi, 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 85607] EDITING : Field date inserts bad font (based on font selection in tools) persistant after change and save
https://bugs.documentfoundation.org/show_bug.cgi?id=85607 --- Comment #7 from QA Administrators --- Dear Antoine BON, 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 90092] FORMATTING & VIEWING: Text and line overlap in paragraph with bottom border after a table in footer
https://bugs.documentfoundation.org/show_bug.cgi?id=90092 --- Comment #8 from QA Administrators --- Dear Gordo, 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 79570] VIEWING: In print preview, page up & page down don't function at specific zoom levels
https://bugs.documentfoundation.org/show_bug.cgi?id=79570 --- Comment #9 from QA Administrators --- Dear Yousuf Philips (jay) (retired), 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 68050] UI: Fields dialog does not preserve scroll position when focussed
https://bugs.documentfoundation.org/show_bug.cgi?id=68050 --- Comment #9 from QA Administrators --- Dear freddi34, 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 46185] VIEWING: Display of Non-Printing Characters is Wrong after Alignment Change
https://bugs.documentfoundation.org/show_bug.cgi?id=46185 --- Comment #18 from QA Administrators --- Dear Harald Koester, 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 61813] Fields wrap to next line improperly
https://bugs.documentfoundation.org/show_bug.cgi?id=61813 --- Comment #13 from QA Administrators --- Dear Bejhan, 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 50289] VIEWING: Background-color of cell overlaps border in page preview / export to PDF / print
https://bugs.documentfoundation.org/show_bug.cgi?id=50289 --- Comment #11 from QA Administrators --- Dear Narigo, 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 45597] FORMATTING: Wrong Paragraph Inserted with Direct Cursor in "Tab and spaces" mode
https://bugs.documentfoundation.org/show_bug.cgi?id=45597 --- Comment #13 from QA Administrators --- Dear Harald Koester, 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 40105] VIEWING: Switching of view layouts causes change of viewing position of document
https://bugs.documentfoundation.org/show_bug.cgi?id=40105 --- Comment #18 from QA Administrators --- Dear Ihar Filipau, 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 37873] VIEWING: Text shifted outside cell by indents or border distance invisible, but printed
https://bugs.documentfoundation.org/show_bug.cgi?id=37873 --- Comment #18 from QA Administrators --- Dear sasha.libreoffice, 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 122421] text in table wasn't aligned when opening a RTF file
https://bugs.documentfoundation.org/show_bug.cgi?id=122421 --- Comment #9 from QA Administrators --- Dear paolo busto, 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 139674] Merge and Center Cells button wastes too much space on the toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=139674 --- Comment #3 from QA Administrators --- Dear Dima, 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 121542] writer picture crop scale ist not stable saved in the file
https://bugs.documentfoundation.org/show_bug.cgi?id=121542 --- Comment #12 from QA Administrators --- Dear Pit Zaclade, 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 119425] Use Ctrl+Tab to switch between sheets on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=119425 --- Comment #18 from QA Administrators --- Dear Heiko Tietze, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 117858] FILESAVE: "Export as EPUB" rotated or scaled images shown in original state (see comment 22)
https://bugs.documentfoundation.org/show_bug.cgi?id=117858 --- Comment #25 from QA Administrators --- Dear Pete, 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 104322] Formulas in tables in Writer not (directly) updating when referred cells are changed
https://bugs.documentfoundation.org/show_bug.cgi?id=104322 --- Comment #12 from QA Administrators --- Dear Butch, 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 100270] SfxModule destructor SfxInterface deletion references invalid objects
https://bugs.documentfoundation.org/show_bug.cgi?id=100270 --- Comment #10 from QA Administrators --- Dear aptitude, 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 150954] Pivot table is gone after the file is saved in xlsx file
https://bugs.documentfoundation.org/show_bug.cgi?id=150954 Aron Budea changed: What|Removed |Added Hardware|x86-64 (AMD64) |All -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123225] Loss of functions in XLSX pivot table's context menu until refreshed (see comment 18)
https://bugs.documentfoundation.org/show_bug.cgi?id=123225 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||0954 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112416] [META] XLSX pivot table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=112416 Aron Budea changed: What|Removed |Added Depends on||150954 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150954 [Bug 150954] Pivot table is gone after the file is saved in xlsx file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112416] [META] XLSX pivot table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=112416 Bug 112416 depends on bug 150954, which changed state. Bug 150954 Summary: Pivot table is gone after the file is saved in xlsx file https://bugs.documentfoundation.org/show_bug.cgi?id=150954 What|Removed |Added Status|RESOLVED|NEW Resolution|DUPLICATE |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150954] Pivot table is gone after the file is saved in xlsx file
https://bugs.documentfoundation.org/show_bug.cgi?id=150954 Aron Budea changed: What|Removed |Added Resolution|DUPLICATE |--- See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||3225 Status|RESOLVED|NEW CC||aron.bu...@gmail.com Blocks||112416 Ever confirmed|0 |1 --- Comment #4 from Aron Budea --- I'd treat this separately from bug 123225, that one's about the behavior in Excel after saving as XLSX, while this is about the behavior in Calc. Ideally both should be fixed, but I doubt fixing one of the two will fix the other as well. Plus the bugdoc in 123225, attachment 149532, doesn't exhibit this issue. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112416 [Bug 112416] [META] XLSX pivot table bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153054] New: Can't install Libre 7.4.3.2
https://bugs.documentfoundation.org/show_bug.cgi?id=153054 Bug ID: 153054 Summary: Can't install Libre 7.4.3.2 Product: LibreOffice Version: unspecified Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mrrjh...@gmail.com Description: Can't install Libre Office on my Win 10 PC using Firefox. Actual Results: Just try installing on a Win 10 64 bit PC. Expected Results: No change Reproducible: Always User Profile Reset: No Additional Info: Should have installed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149163] Track changes in a spreadsheet shows the most recent change in a transaction instead of the change from the start of that transaction.
https://bugs.documentfoundation.org/show_bug.cgi?id=149163 --- Comment #3 from haim kilov --- I think that the initial value (original text that has been updated) should not disappear, especially in the change history. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153051] Improvement of Calc's csv import dialog.
https://bugs.documentfoundation.org/show_bug.cgi?id=153051 m.a.riosv changed: What|Removed |Added Keywords||needsUXEval CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- It could be helpful, specially in those more dubious cases. Let's see what UX/design says. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153053] New: Hiding sections in mail merge with mutiple fields depends defining conditions for database fileds.
https://bugs.documentfoundation.org/show_bug.cgi?id=153053 Bug ID: 153053 Summary: Hiding sections in mail merge with mutiple fields depends defining conditions for database fileds. Product: LibreOffice Version: 3.3.0 release Hardware: IA64 (Itanium) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nalong...@sbcglobal.net Description: In Libre Office help for defining conditions for database fileds, NOT Database.Table.Company & Database.Table.Company EQ "" are considered equivalent. That is true for single fileds but I have found that for 2 or more fields, that is not true. Steps to Reproduce: 1.Insert a section in a writer for mail merge. 2.Insert more than one mail merge field in the section 3.Edit the section to hide it if any of the fileds are missing 4.Enter [Database.Table.Field1]EQ "" OR [Database.Table.Field2] EQ "" Actual Results: If Database.Table.Field1 OR Database.Table.Field2 is missing, the section is not not hidden. Expected Results: If Database.Table.Field1 OR Database.Table.Field2 is missing, the section should be hidden. Reproducible: Always User Profile Reset: No Additional Info: I have found that if I change the code to: NOT[Database.Table.Field1] OR NOT [Database.Table.Field2] and either filed is missing, the section is hidden as expected. Although EQ "" works for single fields, in this case, it does not work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153052] New: Image insert results in two undo actions added to undo stack
https://bugs.documentfoundation.org/show_bug.cgi?id=153052 Bug ID: 153052 Summary: Image insert results in two undo actions added to undo stack Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rayk...@gmail.com Came across this while hacking on enhancement Bug 149073 Steps to repro: 1) Open Calc 2) Insert an image (Menu->Insert->Image...) Results: Two undo actions are added, "Insert image with transparency 'Image 1'" and "Change object name of Image with transparency to 'Image 1'" To see this click on the Undo control drop down in the Standard tool bar or wherever you may have it. Expected results: One undo action added, "Insert image with transparency 'Image 1'" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153051] New: Improvement of Calc's csv import dialog.
https://bugs.documentfoundation.org/show_bug.cgi?id=153051 Bug ID: 153051 Summary: Improvement of Calc's csv import dialog. Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ville...@t-online.de Description: Is it feasible to change the font colors in preview columns while checking the import options? Show columns in blue font (as with value highlighting) if values would be imported as numbers, numeric dates, times, booleans, currencies, percent. Show green font if they would be interpreted as formulas. Steps to Reproduce: 1. Copy 2 lines of text 2. Paste-special into Calc 3. Choose "unformatted text" Actual Results: Mono-color preview in import dialog not indicating if the current settings are appropriate or not. Expected Results: Check "Detect special numbers" and dates in column preview are highlighted in blue. Uncheck "Detect special numbers" and dates in column preview are black again. Reproducible: Always User Profile Reset: No Additional Info: none -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153039] (LO 7.4) Multiple bugs while submitting XML from XForms document
https://bugs.documentfoundation.org/show_bug.cgi?id=153039 --- Comment #7 from Pavel Zhdanovich --- Created attachment 184701 --> https://bugs.documentfoundation.org/attachment.cgi?id=184701=edit updated XForms document with globally available address for submission Done. Please fill free to test the document just attached. My Web application is now publicly available. It changes (literally) "true" to "false" and "41" to "42" everywhere in an XML document it receives via POST/PUT methods. Hope it helps. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77743] FILEOPEN PPTX Custom bullet character not shown due to missing mapping in OpenSymbol
https://bugs.documentfoundation.org/show_bug.cgi?id=77743 --- Comment #17 from Ofir --- Tested with the first attached symbols.pptx. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77743] FILEOPEN PPTX Custom bullet character not shown due to missing mapping in OpenSymbol
https://bugs.documentfoundation.org/show_bug.cgi?id=77743 Ofir changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #16 from Ofir --- I can still reproduce and see rectangles instead of symbols in B. C. D. Version: 7.4.4.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 2; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US Ubuntu package version: 1:7.4.4~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153049] No expanding cell range while scrolling or when pasting outside of viewport
https://bugs.documentfoundation.org/show_bug.cgi?id=153049 --- Comment #2 from Caolán McNamara --- Is this with mouse scroll wheel? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152923] Column and row headings in Calc lost their colored, slightly 3D look
https://bugs.documentfoundation.org/show_bug.cgi?id=152923 --- Comment #4 from Andy --- Sorry for the impatience where could I find some info on the motivation/rationale for this change? Maybe I am just unable to perceive its advantages At the moment, the reasons I see to undo this are instead clear: - it becomes more difficult to distinguish the headings from the editable cells - this way, for instance, a D1 Cell with a centered "D", 8 points size, any sans serif font, a thin border is just identical and undistinguishable from the heading above it. With the previous heading style the chances of this occurring were radically lower. - it gives the general impression of a less well defined and identified allocation of the screen space - finally, I do not want to say that you should always follow others, but neither Excel nor Google Sheets have this kind of "headings invisibility". Having said this, I am eager to try understand what motivated the decision, and open to change my view if I find those reasons convincing. All the best -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152863] Mismatch between ODT and DOCX page layout
https://bugs.documentfoundation.org/show_bug.cgi?id=152863 Luis Xavier Baena Mourão changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Luis Xavier Baena Mourão --- This appears to be how the two editors anchor graphic elements. Will research further. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153034] Two wrong Greek characters in WordPerfect 5 import
https://bugs.documentfoundation.org/show_bug.cgi?id=153034 --- Comment #2 from e...@columbia.edu --- There are three lines with changes in the original commit. I think the first and third lines need to be reverted; but I think the second line MAY correct a real error. I would have take another look at the WP6 code to be certain. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152923] Column and row headings in Calc lost their colored, slightly 3D look
https://bugs.documentfoundation.org/show_bug.cgi?id=152923 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru, ||heiko.tietze@documentfounda ||tion.org --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- Heiko you made this change, if I remember right, and it was an UX dicision. And I don't see any reasons to revert it now @Andy: please be more patient. thanks -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152956] calc table freezing under xls
https://bugs.documentfoundation.org/show_bug.cgi?id=152956 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Ever confirmed|0 |1 CC||79045_79...@mail.ru Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- Please attach your problem XLS here -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135084] Crash on undo ucrtbase abort ('boost::wrapexcept' what(): bad rational: zero denominator)
https://bugs.documentfoundation.org/show_bug.cgi?id=135084 Julien Nabet changed: What|Removed |Added Keywords|wantBacktrace |haveBacktrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135084] Crash on undo ucrtbase abort ('boost::wrapexcept' what(): bad rational: zero denominator)
https://bugs.documentfoundation.org/show_bug.cgi?id=135084 --- Comment #16 from Julien Nabet --- Created attachment 184700 --> https://bugs.documentfoundation.org/attachment.cgi?id=184700=edit gdb bt Here's a bt with console logs retrieved on pc Debian x86-64 with master sources updated today + gen rendering. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153042] FILEOPEN: DOC/X: Incorrect indent of first line
https://bugs.documentfoundation.org/show_bug.cgi?id=153042 Justin L changed: What|Removed |Added Keywords||filter:docx CC||vasily.melenc...@cib.de Summary|FILEOPEN: DOC: Incorrect|FILEOPEN: DOC/X: Incorrect |indent of first line|indent of first line --- Comment #11 from Justin L --- Likely this should be solved by a layout exception - where a numbering tab at position zero with indent/margin/whatever all at zero should be zero width. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150863] after paste special unformatted text, Calc scrolls only visible rows
https://bugs.documentfoundation.org/show_bug.cgi?id=150863 Pierre Fortin changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #6 from Pierre Fortin --- Almost forgot about this issue... I haven't seen this in a while, so closing. The following has surely changed since the original report too... Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 28ff4647e9dac8eebe3a169e828bacc8dc78e363 CPU threads: 20; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded Jumbo -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100584] Add tabs in RTL right-hand
https://bugs.documentfoundation.org/show_bug.cgi?id=100584 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 135084] Crash on undo ucrtbase abort ('boost::wrapexcept' what(): bad rational: zero denominator)
https://bugs.documentfoundation.org/show_bug.cgi?id=135084
Telesto changed:
What|Removed |Added
Summary|Crash on undo ucrtbase |Crash on undo ucrtbase
|abort |abort
||('boost::wrapexcept' what():
||bad rational: zero
||denominator)
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135084] Crash on undo ucrtbase abort
https://bugs.documentfoundation.org/show_bug.cgi?id=135084 Telesto changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #15 from Telesto --- Repro Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 37e3455a13ab5741104bf41d05a80e60a4612682 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 threaded Backtrace would be nice to have -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148377] Crashes soon after opening and choosing icon for picture insertion. I am using the Mac Mini Silicone Processor, 16 gigs ram
https://bugs.documentfoundation.org/show_bug.cgi?id=148377 Telesto changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Telesto --- Please try LibreOffice 7.4.4. Lots of macOS specific are gone. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152945 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152945 [Bug 152945] PDF export of docx which include MS Visio objects -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127182] [META] MS Visio bugs and Improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=127182 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||152945 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152945 [Bug 152945] PDF export of docx which include MS Visio objects -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152945] PDF export of docx which include MS Visio objects
https://bugs.documentfoundation.org/show_bug.cgi?id=152945 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Version|7.5.0.1 rc |6.2 all versions CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Keywords||bibisectRequest, regression Blocks||127182, 103378 --- Comment #1 from Stéphane Guillou (stragu) --- Reproduced. Looks neat and I can select the text in the PDF in: Version: 6.1.0.3 Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group threaded But looks blurry and I can't select the text since 6.2: Version: 6.2.0.0.beta1 Build ID: d1b41307be3f8c19fe6f1938cf056e7ff1eb1d18 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=127182 [Bug 127182] [META] MS Visio bugs and Improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152355] Calc often crashes while editing and scrolling through any document
https://bugs.documentfoundation.org/show_bug.cgi?id=152355 gabrie...@posteo.net changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #4 from gabrie...@posteo.net --- Version information: Version: 7.4.3.2 (x64) / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL I have no idea of what "Skia" stands for, but since you told me how to, I turned it off. I opened 5 or 6 documents today, took the time to scroll through each one several times and everything worked perfectly... but the issue happened so randomly that I can't be sure yet if it's still present. If you consider I began to get used to not scrolling, I guess I'll need a week or so to be sure. Anyway, I already have great hopes! :) Thanks for your help! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 143119, which changed state. Bug 143119 Summary: Writer and Calc (v7.1.4 and v7.2.0) crash when copying content (cmd-C or menu) on macOS if Tamil UI installed https://bugs.documentfoundation.org/show_bug.cgi?id=143119 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Telesto changed: What|Removed |Added CC||julien.malard@mail.mcgill.c ||a --- Comment #94 from Telesto --- *** Bug 143119 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 143119] Writer and Calc (v7.1.4 and v7.2.0) crash when copying content (cmd-C or menu) on macOS if Tamil UI installed
https://bugs.documentfoundation.org/show_bug.cgi?id=143119 Telesto changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #13 from Telesto --- The crash report seen in comment 10 attachment got fixed. Please upgrade to LibreOffice 7.4.4 *** This bug has been marked as a duplicate of bug 148435 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146626] Calc crashes every time on font size operation, in a specific document
https://bugs.documentfoundation.org/show_bug.cgi?id=146626 Telesto changed: What|Removed |Added CC||tele...@surfxs.nl --- Comment #12 from Telesto --- (In reply to Emil Prpic from comment #11) > Hello! > > LibreOffice 7.4.2 on macOS Monterey 12.6 problem still persists. Would you mind to test 7.4.4. A bunch of macOS specific bug got fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150863] after paste special unformatted text, Calc scrolls only visible rows
https://bugs.documentfoundation.org/show_bug.cgi?id=150863 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #5 from Stéphane Guillou (stragu) --- Pierre, are you on Linux using GTK3? I think it might have to do with a change in the GTK scrollbar. Please paste here the information copied from Help > About LibreOffice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153039] (LO 7.4) Multiple bugs while submitting XML from XForms document
https://bugs.documentfoundation.org/show_bug.cgi?id=153039 --- Comment #6 from Pavel Zhdanovich --- Ah, sorry! I've left my document with the local address of my web server 192.168.14.2 in the submission property. This address is reachable inside my local network only. I will expose my web server to Internet in 3-5 hours and attach the new version of the XForms document such that everybody will be able to test it. I apologize for such an awkward situation! Please wait for my update! Thanks for you time! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Telesto changed: What|Removed |Added CC||p...@chiltern.org.uk --- Comment #93 from Telesto --- *** Bug 148069 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 148069] LibreOffice crashes with blank spreadsheet when dragging between screens.
https://bugs.documentfoundation.org/show_bug.cgi?id=148069 Telesto changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Telesto --- Thanks for the report. The issue has been fixed in LibreOffice 7.4.4 *** This bug has been marked as a duplicate of bug 148435 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Telesto changed: What|Removed |Added CC||ken.shirr...@gmail.com --- Comment #92 from Telesto --- *** Bug 152955 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 152955] Pasting into a diagram causes beachball hang on MacBook
https://bugs.documentfoundation.org/show_bug.cgi?id=152955 Telesto changed: What|Removed |Added Resolution|--- |DUPLICATE CC||tele...@surfxs.nl Status|UNCONFIRMED |RESOLVED --- Comment #2 from Telesto --- This should be fixed with LibreOffice 7.4.4 based on the crash reporter information attached *** This bug has been marked as a duplicate of bug 148435 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153029] LanguageTag broken when copying table with text to Calc (causing text to show as misspelled)
https://bugs.documentfoundation.org/show_bug.cgi?id=153029 Telesto changed: What|Removed |Added Version|7.6.0.0 alpha0+ Master |4.0.0.3 release --- Comment #1 from Telesto --- Also in Versie 4.0.0.3 (Bouw-id: 7545bee9c2a0782548772a21bc84a9dcc583b89) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152178] Calc spreadsheet crashes if cursor is scrolled quickly, or off the page. Also crashes when cropping an image, if cropped in two directions
https://bugs.documentfoundation.org/show_bug.cgi?id=152178 --- Comment #3 from Stéphane Guillou (stragu) --- Jeff replied by email: > I believe the previous version was 7.3.7. > A few weeks ago I upgraded to Windows 11. Now Libre is not crashing nearly > as much, in fact I tried to recreate the crash this morning and could not. > Hope this information helps. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150120] FILEOPEN DOCX Embededd OLE object (XLSX spreadsheet) is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=150120 --- Comment #6 from Stéphane Guillou (stragu) --- Can't reproduce either with: Version: 7.3.7.2 / LibreOffice Community Build ID: e114eadc50a9ff8d8c8a0567d6da8f454beeb84f CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11 Locale: de-DE (en_AU.UTF-8); UI: en-US Calc: threaded Nor with: Version: 7.2.7.2 / LibreOffice Community Build ID: 8d71d29d553c0f7dcbfa38fbfda25ee34cce99a2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: de-DE (en_AU.UTF-8); UI: en-US Calc: threaded or: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d04c197b436094844abfa5fb7c12e095165d2bca CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
