[Libreoffice-bugs] [Bug 52352] LibreOffice Spreadsheet V3.5.5.3 Sort Ascending/Descending order BUG
https://bugs.documentfoundation.org/show_bug.cgi?id=52352 --- Comment #4 from Chadamos --- Solve this spr.spreadsheet with ascending or descending order. I never providing you the real plan because https://essay-reviewer.com/best-paper-writing-service/ have some serious things then mark them and put them on top. In this way, you can easily highlight that thing and also can choose it for multiple purposes. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142406] Export chart to empty PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=142406 --- Comment #7 from Harshita Nag --- (In reply to Jack Kuo from comment #5) > @Timur > Thanks for your useful information :) (In reply to Timur from comment #4) > Some QA points: > Reporter should attach sample, not use outside link. > > If someone cannot reproduce, it's not definite conclusion. WorksForMe is > when one can reproduce with older version and cannot with newer. > > If someone else reporduces, it's plain status New. Reopen is when fix > doesn't work. > See https://bugs.documentfoundation.org/page.cgi?id=fields.html#bug_status > > If bug reported for Mac is repro in Linux, we set All. > > Finally, all reporter and testers should first search. > This is a duplicate. > > *** This bug has been marked as a duplicate of bug 111392 *** Okay I will keep it in mind from next time. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142406] Export chart to empty PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=142406 --- Comment #6 from Harshita Nag --- (In reply to Jack Kuo from comment #2) > (In reply to Harshita Nag from comment #1) > > Can't reproduce it in the fresh version. > > > > Version: 7.1.1.2 / LibreOffice Community > > Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 > > CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3 > > Locale: en-IN (en_IN); UI: en-US > > Calc: threaded > > Do you really export it successfully and open the PDF with the correct chart? > I try LibreOffice v7.1.3.2 on Ubuntu 20.04 LTS, fails again. Oh, that was a mistake from my side. I was testing it from the menu. Apologies. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139633] Direct editing of tree nodes in the Navigator to rename objects
https://bugs.documentfoundation.org/show_bug.cgi?id=139633 --- Comment #11 from Jim Raykowski --- Hi Tarun, (In reply to Tarun Sharma from comment #10) > hi jim > for renaming DRAWOJBECT do i have to pass refernce of m_xTreeView, by adding > a new parameter in the execute function??! > > sw/source/uibase/shells/drwbassh.cxx > Handling for this case will also be done in the added edit entry handler IMPL_LINK(SwContentTree, EditedEntryHdl, const IterString&, rIterString, bool) in sw/source/uibase/utlui/content.cxx > How should i validate the inputs currently its using pDlg 's method > setForbiddenChars which was created from CreateSwRenameNamedDlg . > > pDlg(pFact->CreateSwRenameXNamedDlg(m_xTreeView.get(), xNamed, xNameAccess)); Check the rIterString.second for forbidden chars. For bookmark forbidden chars see: sw/source/uibase/inc/bookmark.hxx static constexpr OUStringLiteral aForbiddenChars. If found, break out of the case before setting xNameAccess. Looking forward to seeing the patch! Please submit to gerrit and add me as a reviewer so we can discuss code there. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142156] Default style settings can't be configured.
https://bugs.documentfoundation.org/show_bug.cgi?id=142156 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141436] EDITING: transposed formula object has "size zero" and is in wrong cell
https://bugs.documentfoundation.org/show_bug.cgi?id=141436 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136923] Export to PDF/A is not PDF/A conformant (ISO 19005-1:2005, Clause: 6.1.12, Test number: 5 - Maximum capacity of an array (in elements) is 8191)
https://bugs.documentfoundation.org/show_bug.cgi?id=136923 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142158] External HyperSQL database is read-only when EDITING with non-DBA account
https://bugs.documentfoundation.org/show_bug.cgi?id=142158 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135704] Writer fails to save docx formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=135704 --- Comment #4 from QA Administrators --- Dear r59trevor, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142108] Calc chart loses number formatting on bars when pasted in Writer doc wher shows all decimal parts instead of using original format setting
https://bugs.documentfoundation.org/show_bug.cgi?id=142108 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142149] upper custom first page colontitle lost if I change botton colontitle properties.
https://bugs.documentfoundation.org/show_bug.cgi?id=142149 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135704] Writer fails to save docx formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=135704 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135232] FILEOPEN: PPTX: Image overlaps text with Average font
https://bugs.documentfoundation.org/show_bug.cgi?id=135232 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 135232] FILEOPEN: PPTX: Image overlaps text with Average font
https://bugs.documentfoundation.org/show_bug.cgi?id=135232 --- Comment #9 from QA Administrators --- Dear Rhys Young, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134899] FILEOPEN DOCX: Checkbox content control takes less space than original
https://bugs.documentfoundation.org/show_bug.cgi?id=134899 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124461] Creating workbook to workbook links no longer simple.
https://bugs.documentfoundation.org/show_bug.cgi?id=124461 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134899] FILEOPEN DOCX: Checkbox content control takes less space than original
https://bugs.documentfoundation.org/show_bug.cgi?id=134899 --- Comment #8 from QA Administrators --- Dear rominator, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124461] Creating workbook to workbook links no longer simple.
https://bugs.documentfoundation.org/show_bug.cgi?id=124461 --- Comment #15 from QA Administrators --- Dear Bob, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 138401] Strange colours in patches on libreoffice
https://bugs.documentfoundation.org/show_bug.cgi?id=138401 --- Comment #3 from QA Administrators --- Dear Richard, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 138009] Cross-Reference in Header: If the value somewhere on the page changes, the header remains unchanged
https://bugs.documentfoundation.org/show_bug.cgi?id=138009 --- Comment #2 from QA Administrators --- Dear canned, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 132884] Segmentation Fault after python+uno script closes in case desktop is not terminated
https://bugs.documentfoundation.org/show_bug.cgi?id=132884 --- Comment #2 from QA Administrators --- Dear Suren Arustamyan, 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 72604] Fax-Wizard - Personal Data are only partial adopted
https://bugs.documentfoundation.org/show_bug.cgi?id=72604 --- Comment #17 from QA Administrators --- Dear Andreas Mantke, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125342] Excel 5.0/95 XLS File shows messy code in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=125342 --- Comment #6 from QA Administrators --- Dear Kevin Suo, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125276] Certain document with embedded sheets freezes for a while, when scrolling past a certain page
https://bugs.documentfoundation.org/show_bug.cgi?id=125276 --- Comment #5 from QA Administrators --- Dear Buovjaga, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125336] Paragraph indent used twice when positioning frame
https://bugs.documentfoundation.org/show_bug.cgi?id=125336 --- Comment #5 from QA Administrators --- Dear ajlittoz, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 123375] Multi-line Calc cell split into one cell per original cell line when deleted and copied using Ctrl-X and Ctrl-V
https://bugs.documentfoundation.org/show_bug.cgi?id=123375 --- Comment #11 from QA Administrators --- Dear johlson, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113811] FILESAVE: dialogs are not preserved in flat ODS file
https://bugs.documentfoundation.org/show_bug.cgi?id=113811 --- Comment #10 from QA Administrators --- Dear Mátyás Jani, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 112075] Problems with element in flat ODF
https://bugs.documentfoundation.org/show_bug.cgi?id=112075 --- Comment #5 from QA Administrators --- Dear Regina Henschel, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106468] editing viewing fileopen unable to open edit or view older wordperfect documents
https://bugs.documentfoundation.org/show_bug.cgi?id=106468 --- Comment #7 from QA Administrators --- Dear sandhillsinvestment, 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://kiwiirc.com/nextclient/irc.freenode.net/#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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142418] 1.2 - 1.1 = 0.09 ?
https://bugs.documentfoundation.org/show_bug.cgi?id=142418 --- Comment #2 from damontrip...@gmail.com --- Created attachment 172241 --> https://bugs.documentfoundation.org/attachment.cgi?id=172241=edit screenshot of issue -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142418] 1.2 - 1.1 = 0.09 ?
https://bugs.documentfoundation.org/show_bug.cgi?id=142418 damontrip...@gmail.com changed: What|Removed |Added CC||damontrip...@gmail.com --- Comment #1 from damontrip...@gmail.com --- Created attachment 172240 --> https://bugs.documentfoundation.org/attachment.cgi?id=172240=edit calc sheet demonstrating issue -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142418] New: 1.2 - 1.1 = 0.09 ?
https://bugs.documentfoundation.org/show_bug.cgi?id=142418 Bug ID: 142418 Summary: 1.2 - 1.1 = 0.09 ? Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: damontrip...@gmail.com Description: 1.2 - 1.1 = 0.09 ? Steps to Reproduce: 1. enter 1.2 2. enter -1.1 3. sum above Actual Results: 0.09 Expected Results: 0.1 Reproducible: Always User Profile Reset: No Additional Info: does not occur with 0.2 - 0.1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142406] Export chart to empty PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=142406 --- Comment #5 from Jack Kuo --- @Timur Thanks for your useful information :) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142417] New: Online Help: "File Conversion Filter Names" page should contain an "API Name" column
https://bugs.documentfoundation.org/show_bug.cgi?id=142417 Bug ID: 142417 Summary: Online Help: "File Conversion Filter Names" page should contain an "API Name" column Product: LibreOffice Version: 7.2.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: suokunl...@126.com CC: olivier.hal...@libreoffice.org The following API documentation page: https://api.libreoffice.org/docs/idl/ref/servicecom_1_1sun_1_1star_1_1document_1_1MediaDescriptor.html#a777c03d61101090a1539aafc6ba1c4ca says that the FilterName option passed using com.sun.star.beans.PropertyValue should be an internal filter name and references to the following Online Help page: https://help.libreoffice.org/latest/en-US/text/shared/guide/convertfilters.html However, the Filter Names as listed on this Online Help page are actually UI Names (or Localized Names) of those filters, not API Names. For instance: * on the online help page the Filter Name for ODT is "Writer 8", but according to filter/source/config/fragments/filters/writer8.xcu in the source code the API name for ODT should be "writer8". The API name should be used in the MediaDescriptor::FilterName rather than the UI name, otherwise the API calling will be wrong and the API then falls back to the default fiter. * Online help page says "Word 2007–365", but the API name should be "MS Word 2007 XML". The solution is not to revise those names on Online Help to those UI names, but to add a new column indicating their corresponding API Names, just like the OpenOffice wiki page did: https://wiki.openoffice.org/wiki/Framework/Article/Filter/FilterList_OOo_3_0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134675] [EDITING] Whole column cannot be pasted to a column range over 23 selected by shift-click
https://bugs.documentfoundation.org/show_bug.cgi?id=134675 --- Comment #8 from Eike Rathke --- (In reply to Timur from comment #5) > This is closest to WontFix. Actually no. I'd rather have this case of copy-pasting entire columns onto entire columns covered and exempted. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134675] [EDITING] Whole column cannot be pasted to a column range over 23 selected by shift-click
https://bugs.documentfoundation.org/show_bug.cgi?id=134675 --- Comment #7 from Eike Rathke --- (In reply to zzz from comment #6) > The mere fact that just figuring out the cause of > this case took one year is a good evidence. Nonsense. I was made aware of this just today by being Cc'ed with comment 3. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 136923] Export to PDF/A is not PDF/A conformant (ISO 19005-1:2005, Clause: 6.1.12, Test number: 5 - Maximum capacity of an array (in elements) is 8191)
https://bugs.documentfoundation.org/show_bug.cgi?id=136923
--- Comment #6 from sl.lebl...@free.fr ---
Hello,
Please excuse my bad English but I am French.
Looks like I have the same problem.
When I try to macro export a report (base) to pdf.
With "Selectpdfversion, 1", I have a pdf / A compliance error
With "Selectpdfversion, 2" I have no error, but the value of form fields are
not displayed.
The macro I am using is as follows:
Sub convertirPDF()
Dim Adresse As String
Dim props As Variant, propsFiltre As Variant
propsFiltre = CreateProperties(Array("SelectPdfVersion",1 ))
props = CreateProperties(Array("FilterName", "writer_pdf_Export",
"FilterData", propsFiltre() ))
Adresse = convertToURL("le chemin et le nom du fichier PDF avec
l'extention")
ThisComponent.storeToURL(Adresse, props())
End Sub
Function CreateProperties(propList() As Variant) As Object
Dim n as long, x as long
n = UBound(propList)
if n < 0 then
CreateProperties = Array()
else
if (n and 1) = 0 then
MsgBox("Erreur : nombre impair d'arguments", 16,
"CreateProperties")
else
Dim p(n\2) As New com.sun.star.beans.PropertyValue
for x = 0 to n\2
p(x).Name = propList(2*x)
p(x).Value = propList(2*x +1)
next
CreateProperties = p()
end if
end if
End Function
--
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142180] Invalid text comparison result in Basic
https://bugs.documentfoundation.org/show_bug.cgi?id=142180 Joshua Williams changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |joshmackwilliams@protonmail |desktop.org |.com -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142416] New: Using mouse click in a base to launch a macro from a cell in a table control does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=142416 Bug ID: 142416 Summary: Using mouse click in a base to launch a macro from a cell in a table control does not work Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d...@dmcnamara.net Description: Macros run from buttons. the macro that will not launch will run when manually started. Steps to Reproduce: 1. mouse click on cell 2. 3. Actual Results: Nothing Expected Results: Run macro Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142415] New: Using mouse click in a base to launch a macro from a cell in a table control does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=142415 Bug ID: 142415 Summary: Using mouse click in a base to launch a macro from a cell in a table control does not work Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: d...@dmcnamara.net Description: Macros run from buttons. the macro that will not launch will run when manually started. Steps to Reproduce: 1. mouse click on cell 2. 3. Actual Results: Nothing Expected Results: Run macro Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142414] EDITING: drag and drop does not work inside a slide
https://bugs.documentfoundation.org/show_bug.cgi?id=142414 Rocco Santoro changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142414] New: EDITING: drag and drop does not work inside a slide
https://bugs.documentfoundation.org/show_bug.cgi?id=142414 Bug ID: 142414 Summary: EDITING: drag and drop does not work inside a slide Product: LibreOffice Version: 6.4.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rocco.sant...@sis-statistica.org Description: I can't drag and drop a text or its part inside a slide with layout title and content. The mouse highlights the text only and the selection vanishes when i am beginning the drag Steps to Reproduce: 1. to select of the text with mouse 2. to try to drag the selection 3. the selection vanishes Actual Results: the text remains the same position Expected Results: the text should move into a new position Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: OpenGL vendor string: X.Org OpenGL renderer string: AMD RAVEN (DRM 3.38.0, 5.8.0-53-generic, LLVM 11.0.0) OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.2.6 OpenGL core profile shading language version string: 4.60 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.2.6 OpenGL shading language version string: 4.60 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.2.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120703] Bugs found by PVS-Studio static analyzer
https://bugs.documentfoundation.org/show_bug.cgi?id=120703 Mike Kaganski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #179 from Mike Kaganski --- (In reply to Roman Kuznetsov from comment #178) Yes, let's close this. Indeed, I didn't manage to fix everything; but the code diverged considerably, and it became increasingly difficult to follow the log. If PVS-Studio people would find time and energy to re-check current master, it would be very welcome, and it would best be tracked in a new issue. Thanks PVS-Studio team! :-) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 100366] [META] Impress/Draw table bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=100366 pavlog changed: What|Removed |Added Depends on||141886 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141886 [Bug 141886] Data saving error in latest updates 7.1.2 & 7.1.1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141886] Data saving error in latest updates 7.1.2 & 7.1.1
https://bugs.documentfoundation.org/show_bug.cgi?id=141886 pavlog changed: What|Removed |Added Status|UNCONFIRMED |NEW Blocks||100366 Ever confirmed|0 |1 Whiteboard| QA:needsComment| CC||pavlograd...@gmail.com --- Comment #2 from pavlog --- Thanks for reporting, I see this behavior in Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 6e6e531b564cdc9d5b25287c215cdc5a1fcbb346 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL and in Version: 7.1.2.2 (x64) / LibreOffice Community Build ID: 8a45595d069ef5570103caea1b71cc9d82b2aae4 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100366 [Bug 100366] [META] Impress/Draw table bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128199] [EMF] Content of EMF image, generated by ESRI ArcMap 2004 is not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=128199 Bartosz changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142413] New "Search Commands" feature: Backspace key launching "Delete Contents" window
https://bugs.documentfoundation.org/show_bug.cgi?id=142413 --- Comment #1 from Rafael Lima --- Created attachment 172239 --> https://bugs.documentfoundation.org/attachment.cgi?id=172239=edit Video showing the bug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142413] New: New "Search Commands" feature: Backspace key launching "Delete Contents" window
https://bugs.documentfoundation.org/show_bug.cgi?id=142413 Bug ID: 142413 Summary: New "Search Commands" feature: Backspace key launching "Delete Contents" window Product: LibreOffice Version: 7.2.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com I am testing the new "Search Commands" feature and I found an unexpected behavior. 1) Open the feature by going to "Help > Search Commands" 2) Start typing a command: e.g. "Format" 3) Press the "Backspace" key 4) Instead of deleting the "Format" word, the "Delete Contents" window is opened. Also, another possible bug. The shortcut Ctrl+F1 is not working to launch the Search Commands. If anyone can confirm this, I can prepare a separate report for it. System information: Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: 128f67e0efa02294205a1abe1be874557ecdcecd CPU threads: 16; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-05-19_06:21:05 Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84726] [META] LibreOffice for Android most annoying bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=84726 Bug 84726 depends on bug 106370, which changed state. Bug 106370 Summary: Android: add ability to insert pictures https://bugs.documentfoundation.org/show_bug.cgi?id=106370 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120941] PPTX with dashed line exported to a large size SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=120941 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #12 from Roman Kuznetsov <79045_79...@mail.ru> --- 471 kb in Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 58b0c95ad50139a62bddb348d10f94053c09cd5b CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded so still repro -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 140574] [EMF] Image has wrong background colour
https://bugs.documentfoundation.org/show_bug.cgi?id=140574 Bartosz changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120703] Bugs found by PVS-Studio static analyzer
https://bugs.documentfoundation.org/show_bug.cgi?id=120703 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru, ||mikekagan...@hotmail.com --- Comment #178 from Roman Kuznetsov <79045_79...@mail.ru> --- Mike, can we close it as fixed? Or there are some unfixed things here? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124690] Renaming a master page does not update the "master pages" pane
https://bugs.documentfoundation.org/show_bug.cgi?id=124690 --- Comment #3 from Roman Kuznetsov <79045_79...@mail.ru> --- still repro in Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 58b0c95ad50139a62bddb348d10f94053c09cd5b CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118887] CALC: Read Combo chart that has multiple series of data from XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=118887 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added CC||79045_79...@mail.ru --- Comment #6 from Roman Kuznetsov <79045_79...@mail.ru> --- still repro in Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community Build ID: 58b0c95ad50139a62bddb348d10f94053c09cd5b CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134675] [EDITING] Whole column cannot be pasted to a column range over 23 selected by shift-click
https://bugs.documentfoundation.org/show_bug.cgi?id=134675 --- Comment #6 from zzz --- 42 should be fine, it's the solution to the whole universe:-) Well, I am very surprised that such magic number is embedded, especially in a spreadsheet software. Arbitrary limitations like that will eventually bring all kinds of perils. The mere fact that just figuring out the cause of this case took one year is a good evidence. Anyway, thanks for proposing a workaround. The problem with such a single-row target area is that it is counter-intuitive. I usually do the copy-column when I want to replicate the column width. For a single row target: (a)If the source is a finite range of rows, then the target column width does NOT change. (b)If the source is an infinite range of rows, then the target column width DOES change to the source width. So user must remember this whole inconsistency. It is also inconsistent with the interface of how to insert new columns, and how to insert-paste. This is how you have to teach users now: - If you want to insert-replicate columns, first consider whether you want to make over 23 columns. If no, then select the source columns, command-copy, then select the target region by selecting some arbitrarily finite rows, such as B1:EZ1, and then command paste. Oh, when you paste, don't forget to set the PasteSpecial|Selection|Formats|On, otherwise you will fail and have to do it again. Now, if you want to make over 23 columns, then you have to do another preparation. First insert the extra columns you want to add, then do the same procedure as above, ie. select the source columns, command-copy, then select the target region by selecting some arbitrarily finite rows, such as B1:EZ1, and then command paste. Oh, when you paste, don't forget to set the PasteSpecial|Selection|Formats|On, otherwise you will fail and have to do it again. Oh, wait, first check the release note because the limitation may have changed to 42. The URL of the release note is... Who wants to make such manual, help tooltip, or do such tutoring? Quite unproductive. Conclusion: The usefulness and ease-of-learn of spreadsheets stem from their fundamental mental model: "Any amount of empty cells can be treated as really empty". So keep that. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139000] Visual artifacts in gradient while scrolling up and down
https://bugs.documentfoundation.org/show_bug.cgi?id=139000 Aron Budea changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #8 from Aron Budea --- Verified in LO Version: 7.2.0.0.alpha1+ (185f3e3c382e93be4e0588ac8a927ea3140bce91) / Ubuntu. Thanks for fixing, Luboš! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141105] LibreOffice versions 7.x.x, Calc resizing columns.
https://bugs.documentfoundation.org/show_bug.cgi?id=141105 --- Comment #3 from Motim --- Hello, Just for your information: (With reference to issue 141105, declared as double) Checking the 7.1.4, 7.1.5 and 7.2.0 dev. (x64) versions. After downloading those files, extracted each one as a portable program. On starting they gave an error notice "Missing file vcruntime140_1.dll", please see attached screenshot. Found such file in some other program I have, pasted it into the program folder and it worked. The resize columns in 'Calc' spreadsheet in RTL position are fine. The new menu is nice. Just another thing, in 'Calc' spreadsheet version 7.2.0. the mouse poiner is visible only on the toolbar and columns headings. Thanks Motim -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141105] LibreOffice versions 7.x.x, Calc resizing columns.
https://bugs.documentfoundation.org/show_bug.cgi?id=141105 --- Comment #2 from Motim --- Created attachment 172238 --> https://bugs.documentfoundation.org/attachment.cgi?id=172238=edit Missing File in LibreOffice 7.1.4, 7.1.5 & 7.2.0.jpg Hello, (Sorry, do not know where to post this info, if its in the wrong place, I apologize) Just for your information: (With reference to issue 141105, declared as double) Checking the 7.1.4, 7.1.5 and 7.2.0 dev. (x64) versions. After downloading those files, extracted each one as a portable program. On starting they gave an error notice "Missing file vcruntime140_1.dll", please see attached screenshot. Found such file in some other program I have, pasted it into the program folder and it worked. The resize columns in 'Calc' spreadsheet in RTL position are fine. The new menu is nice. Just another thing, in 'Calc' spreadsheet version 7.2.0. the mouse poiner is visible only on the toolbar and columns headings. Thanks Motim -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 141436] EDITING: transposed formula object has "size zero" and is in wrong cell
https://bugs.documentfoundation.org/show_bug.cgi?id=141436 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from BogdanB --- Confirm with Version: 7.2.0.0.alpha1+ / LibreOffice Community Build ID: b238522ca121ca8f863fe4d3394ade088a65ad01 CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-US (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103512] [META] AutoFilter-related bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103512 Bug 103512 depends on bug 142350, which changed state. Bug 142350 Summary: EDITING Autofilter enables (empty) filtering if filtering for 0 is also enabled in a range containing empty cells https://bugs.documentfoundation.org/show_bug.cgi?id=142350 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142412] Bulleted lists not obeying Indents & Spacing inherited from Text Body Style
https://bugs.documentfoundation.org/show_bug.cgi?id=142412 Dave changed: What|Removed |Added CC||dhorton...@gmail.com --- Comment #1 from Dave --- Created attachment 172237 --> https://bugs.documentfoundation.org/attachment.cgi?id=172237=edit Screenshot of bulleted list text spilling past the after text indent. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 115893] LO Base Report Builder Does Not Display CLOB (memo field) Data of External HSQLDB and Firebird (embedded / file)
https://bugs.documentfoundation.org/show_bug.cgi?id=115893 --- Comment #21 from trowelandmatt...@yahoo.co.uk --- (... and to confirm, this is still the behavior in LO 7.1.3.2 ) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142411] New: LibreOffice paste unformatted text results in Chinese (simplified)
https://bugs.documentfoundation.org/show_bug.cgi?id=142411 Bug ID: 142411 Summary: LibreOffice paste unformatted text results in Chinese (simplified) Product: LibreOffice Version: 7.1.3.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: luancarvalhomart...@gmail.com Description: Pasting text with Ctrl+Shift+v and selecting Unformatted Text pastes Chinese (simplified). Using Formatted text or regular Ctrl+v pastes in regular text. This happens in Impress, Writter and Calc, but only under KDE Plasma Wayland. System info Operating System: Kubuntu 21.04 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-17-generic OS Type: 64-bit Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-1035G1 CPU @ 1.00GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Steps to Reproduce: 1. Open Writter under KDE Plasma Wayland 2. Copy text 3. Paste with Ctrl+Shift+v 4. Select "Unformatted Text" Actual Results: Text is pasted as Chinese (simplified) Expected Results: Text to be pasted as the current language Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: The issue only happens under KDE Plasma Wayland. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142412] New: Bulleted lists not obeying Indents & Spacing inherited from Text Body Style
https://bugs.documentfoundation.org/show_bug.cgi?id=142412 Bug ID: 142412 Summary: Bulleted lists not obeying Indents & Spacing inherited from Text Body Style Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dhorton...@gmail.com Description: I have a document with wide space on the right side for margin notes. I did it like this: * Default Page Style is modified to have a right margin of 0.5". * Text Body paragraph style is modified to have an "After text" indent of 2.3". This results in a wide white space area on the right side of the page. I can insert a margin note by adding a 1.8" wide frame and setting its horizontal position to "Right". This puts the frame about in the middle of the right margin area. Everything is perfect until I add a bulleted list to the body of the document. If the text for the bullet points is too long it continues until it reaches the right margin of the page before wrapping. Since the List style inherits from Text Body, I would expect it to obey the 2.3" after text indent I set with Text Body. In fact, the style for List shows an after text indent of 2.3", but it does not indent on the page. Steps to Reproduce: 1. Alter Text Body style to have an after text indent of some non-zero value. 2. Type some text and notice how it is pushed away from the right side by the amount set by the after text indent. 3. Add a bulleted list and notice how long lines of text continue to flow up to the page margin, disregarding the inherited after text indent. Actual Results: Long bulleted lists do not wrap in accordance with after text indent. Expected Results: Long bulleted lists should wrap at the same point as the non-bulleted text, because they inherit the style from text body. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.1.2 (x64) / LibreOffice Community Build ID: fe0b08f4af1bacafe4c7ecc87ce55bb426164676 CPU threads: 8; OS: Windows 10.0 Build 19041; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139000] Visual artifacts in gradient while scrolling up and down
https://bugs.documentfoundation.org/show_bug.cgi?id=139000 --- Comment #7 from Commit Notification --- Luboš Luňák committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/887f1dbbda9dd371f52111c2f5a3bbbc67fc5615 properly draw only parts of FillGradientPrimitive2D (tdf#139000) It will be available in 7.1.5. 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139000] Visual artifacts in gradient while scrolling up and down
https://bugs.documentfoundation.org/show_bug.cgi?id=139000 Commit Notification changed: What|Removed |Added Whiteboard|target:7.2.0|target:7.2.0 target:7.1.5 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 96789] Android Viewer keyboard covers text if text at end of the odt file
https://bugs.documentfoundation.org/show_bug.cgi?id=96789 --- Comment #4 from Michael Weghorn --- (In reply to Michael Weghorn from comment #3) > I cannot reproduce this ... ... with Android Viewer self-compiled from git master as of commit 128f67e0efa02294205a1abe1be874557ecdcecd, that is. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 96789] Android Viewer keyboard covers text if text at end of the odt file
https://bugs.documentfoundation.org/show_bug.cgi?id=96789 Michael Weghorn changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED CC||m.wegh...@posteo.de --- Comment #3 from Michael Weghorn --- I cannot reproduce this and from how I understand it, this works as expected because AndroidManifest.xml now has android:windowSoftInputMode="adjustResize" so this was presumably fixed by commit 985474a03f902e088d25e005a7d6499037ed8e12 Author: Ximeng Zu Date: Wed Aug 2 11:23:55 2017 -0500 [Android Viewer] Fix windowSoftInputMode Fix the wrong parameter in AndroidManifest. When changing android:windowSoftInputMode, one should not specify multiple "adjust..." or "state...". Change-Id: I0dcacd846d4fe5c2976fe1708b29086b98f2607b Reviewed-on: https://gerrit.libreoffice.org/40686 Tested-by: Jenkins Reviewed-by: Tomaž Vajngerl The commit message in my pending Gerrit change https://gerrit.libreoffice.org/c/core/+/115973/1 has some more information on that since I came across this while looking into tdf#106893. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142401] LibreOffice writer: stucks forever when collapsing between pages on Windows 7
https://bugs.documentfoundation.org/show_bug.cgi?id=142401 Michael Warner changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Michael Warner --- Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142401] LibreOffice writer: stucks forever when collapsing between pages on Windows 7
https://bugs.documentfoundation.org/show_bug.cgi?id=142401 --- Comment #1 from Michael Warner --- No repro in: Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 6; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded However, I am using a mouse and keyboard, not a touch screen. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=89606 Dieter changed: What|Removed |Added Depends on||142114 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=142114 [Bug 142114] TOC doesn't take into account hidden characters, that are visible as formatting marks -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142114] TOC doesn't take into account hidden characters, that are visible as formatting marks
https://bugs.documentfoundation.org/show_bug.cgi?id=142114 Dieter changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Blocks||89606 Keywords||needsDevEval Summary|Wrong page numbers in TOC |TOC doesn't take into |when printed / saved as PDF |account hidden characters, |due to hidden text |that are visible as ||formatting marks --- Comment #4 from Dieter --- (In reply to temporary2017 from comment #3) > Dieter, when you open the document, is Header 2 on page 2? > Do you see the paragraphs with hidden blue 'a's? Thanks for screenshot. It's always good, to provide detailed steps to reproduce 1. Open attachment 171677 2. Make sure, that hidden characters are displayed (Tools => Options => LibreOffice Writer => Formatting Aids 3. Update index(perhaps not necessary) 4. Export to PDF Actual result: In PDF page number of chapter 2 is "2", although it is part of page I'm not a developer, so I'm not sure, if it is possible that TOC takes into account hidden characters. So perhaps a WONTFIX, but let's ask developers Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 1675a68526c43c6c6e4dc850ee911f0c1de75c88 CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89606 [Bug 89606] [META] Table of Contents and Indexes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128199] [EMF] Content of EMF image, generated by ESRI ArcMap 2004 is not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=128199 Bartosz changed: What|Removed |Added Summary|[EMF] Content of EMF image |[EMF] Content of EMF image, |is not visible from DOCX or |generated by ESRI ArcMap |if inserted in ODT |2004 is not visible |(Generated by ESRI ArcMap | |2004) | -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128199] [EMF] Content of EMF image is not visible from DOCX or if inserted in ODT (Generated by ESRI ArcMap 2004)
https://bugs.documentfoundation.org/show_bug.cgi?id=128199 Bartosz changed: What|Removed |Added Summary|[EMF] Content of EMF image |[EMF] Content of EMF image |is not visible from DOCX or |is not visible from DOCX or |if inserted in ODT |if inserted in ODT ||(Generated by ESRI ArcMap ||2004) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134675] [EDITING] Whole column cannot be pasted to a column range over 23 selected by shift-click
https://bugs.documentfoundation.org/show_bug.cgi?id=134675 --- Comment #5 from Timur --- This is closest to WontFix. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142222] Base crashes when trying to edit records
https://bugs.documentfoundation.org/show_bug.cgi?id=14 --- Comment #7 from Cecil Carpenter --- No, there are no combo boxes in any of the forms for the database file in question. I suppose I can find out how to make the package maintainers aware of this problem with LO Base 6.4.7.2, but do you know that off hand? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106893] Black area when closing bottom toolbar after a change
https://bugs.documentfoundation.org/show_bug.cgi?id=106893 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | Status|NEW |ASSIGNED --- Comment #7 from Michael Weghorn --- With current git master, I can reproduce the issue like this: 1. Open a document (.docx or .odt) 2. tap into the document so that the editing toolbar appears 3. tap the soft keyboard icon in the editing toolbar 4. type some text 5. Touch the soft keyboard button again 5. There is black area (which was covered by soft keyboard before) Version: 7.2.0.0.alpha1+ Build ID: 128f67e0efa0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134675] [EDITING] Whole column cannot be pasted to a column range over 23 selected by shift-click
https://bugs.documentfoundation.org/show_bug.cgi?id=134675 --- Comment #4 from Eike Rathke --- What magic number would you like instead? 42? I chose the discordian 23 because it breaks up something.. The point in this behaviour is to prevent a "paste something into the entire selected range". Which happens if only one cell (or a range of data) was copied, pasting that onto entire selected columns will repeat the data over the selection to fill it up. Which usually leads to out of memory. Having copied an entire column first including all empty cells is a somewhat special case though (there can be no repetition). Which that checking code does not know about. Fwiw, pasting such copied entire columns works if the target range is not selected as entire columns but only as first cell starting positions like in any other normal paste operation, e.g. B1:EZ1 (hit Shift+Ctrl+T to focus the Name Box and enter B1:EZ1 and hit Enter, after which the range is selected). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142114] Wrong page numbers in TOC when printed / saved as PDF due to hidden text
https://bugs.documentfoundation.org/show_bug.cgi?id=142114 --- Comment #3 from temporary2...@homolog.de --- Dieter, when you open the document, is Header 2 on page 2? Do you see the paragraphs with hidden blue 'a's? If not, then you have to make the hidden text visible on your screen by enabling the option "Hidden characters" which can be found under Tools | Options | LibreOffice Writer | Formatting Aids | Display Formatting It is also important to save the document locally. LibreOffice does not apply this change when the document is opened right from the download - at least on my computer. Note, that the above option makes the hidden text visible on the screen only. It remains hidden in the PDF, in the print preview and in the printout. Hence, the TOC should react accordingly to this difference. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142114] Wrong page numbers in TOC when printed / saved as PDF due to hidden text
https://bugs.documentfoundation.org/show_bug.cgi?id=142114 --- Comment #2 from temporary2...@homolog.de --- Created attachment 172234 --> https://bugs.documentfoundation.org/attachment.cgi?id=172234=edit Screenshot of the document - ensure that your settings makes it looking like this -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142294] MAILMERGE: Starting "Insert → Field → More Fields" second time leads to hang of LO.
https://bugs.documentfoundation.org/show_bug.cgi?id=142294 Caolán McNamara changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139000] Visual artifacts in gradient while scrolling up and down
https://bugs.documentfoundation.org/show_bug.cgi?id=139000 Luboš Luňák changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139000] Visual artifacts in gradient while scrolling up and down
https://bugs.documentfoundation.org/show_bug.cgi?id=139000 --- Comment #6 from Commit Notification --- Luboš Luňák committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/9bf9fea0afadef0912d38f0d08b2bf2959569100 properly draw only parts of FillGradientPrimitive2D (tdf#139000) It will be available in 7.2.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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 139000] Visual artifacts in gradient while scrolling up and down
https://bugs.documentfoundation.org/show_bug.cgi?id=139000 Commit Notification changed: What|Removed |Added Whiteboard||target:7.2.0 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 132248] Image or frame wrap settings do not work in footnotes area
https://bugs.documentfoundation.org/show_bug.cgi?id=132248 --- Comment #10 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/512da58e5ce822744e4d0b8139595baf1c623035 sw: layout: fix footnote UAF on tdf132248-3.odt (also, tdf134127-1.odt) It will be available in 7.1.5. 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134127] Tables cannot be created in the footnotes or endnotes areas
https://bugs.documentfoundation.org/show_bug.cgi?id=134127 Commit Notification changed: What|Removed |Added Whiteboard|target:7.2.0|target:7.2.0 target:7.1.5 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 134127] Tables cannot be created in the footnotes or endnotes areas
https://bugs.documentfoundation.org/show_bug.cgi?id=134127 --- Comment #3 from Commit Notification --- Michael Stahl committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/512da58e5ce822744e4d0b8139595baf1c623035 sw: layout: fix footnote UAF on tdf132248-3.odt (also, tdf134127-1.odt) It will be available in 7.1.5. 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 132248] Image or frame wrap settings do not work in footnotes area
https://bugs.documentfoundation.org/show_bug.cgi?id=132248 Commit Notification changed: What|Removed |Added Whiteboard|target:7.2.0|target:7.2.0 target:7.1.5 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142410] FILEOPEN Incorrect display of images in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=142410 marius.gusci...@gmail.com changed: What|Removed |Added Hardware|All |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142410] FILEOPEN Incorrect display of images in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=142410 --- Comment #1 from marius.gusci...@gmail.com --- Created attachment 172233 --> https://bugs.documentfoundation.org/attachment.cgi?id=172233=edit File which shows the problem -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142410] New: FILEOPEN Incorrect display of images in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=142410 Bug ID: 142410 Summary: FILEOPEN Incorrect display of images in Calc Product: LibreOffice Version: 7.1.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: marius.gusci...@gmail.com Description: I have a pretty sizeable xlsx file with a lot of small images that are part of the table. Calc for some reason shows wrong image anchor after row 1675. I've tried manually fixing few images and saving the xlsx but after reopening xlsx same problem appeared again for all the images after row 1675. MS Excel properly shows the images. https://www80.zippyshare.com/v/OEcsYkpD/file.html Steps to Reproduce: 1. Download xlsx file from https://www80.zippyshare.com/v/OEcsYkpD/file.html 2. Open it in Calc 3. Go to row 1675 and observe that all following images have wrong anchor points. Actual Results: After the row 1675 all of the images have wrong anchor point and appear to be broken Expected Results: All of the images are anchored to proper cells Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.1.3.2 (x64) / LibreOffice Community Build ID: 47f78053abe362b9384784d31a6e56f8511eb1c1 CPU threads: 8; OS: Windows 10.0 Build 19042; UI render: Skia/Vulkan; VCL: win Locale: lt-LT (lt_LT); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 106370] Android: add ability to insert pictures
https://bugs.documentfoundation.org/show_bug.cgi?id=106370 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | --- Comment #7 from Michael Weghorn --- (In reply to Tomaz Vajngerl from comment #5) > There are issues in Writer regarding inserting of images, so it is not > completely solved yet. Maybe we should close this bug and open a new one > which is more specific? It shouldn't be the problem of inserting images > itself but rather an Android specific issue which boils down that something > Android build doesn't enable or include (reason is that LO Online works fine > using the same UNO commands). So I would say it is solved, just another > issue is preventing it to be completely fully functional... I don't think it has much to do with the problem that back existed in 2018, but this pending change makes inserting pictures work by now: https://gerrit.libreoffice.org/c/core/+/115932 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 98590] Confusing behavior when cell with number is changed to format Text: no indication if cell value type is number or text
https://bugs.documentfoundation.org/show_bug.cgi?id=98590 --- Comment #14 from Mike Kaganski --- (In reply to b. from comment #13) > let's say there are two options, > > A - immediate reaction on cell format change, with a chance for the user to > see that his changes have been 'accepted', 'worked', and in case of an error > to see it immediately (not sure, but have a chance) ... Let us remember this "not sure", and keep reading: > and B: where the user's changes are not processed at first, so he thinks 'it > didn't work' and 'blindly' throws other changes behind that make everything > worse, only to be surprised months or years later ... So if one uses correct terms, there are two options: A: when user has chances to *not* see (overlook) important problems, to find out later - when it's too late, after some saves, that the data is irreversibly damaged; and B: where user is *guaranteed* to see immediately that they use *wrong* tool - formatting - for the task of converting data (for which there are *dedicated* tools). Yes, some people are too clever to read documentation, or to ask on forums, and would "'blindly' throws other changes behind that make everything worse, only to be surprised months or years later" - but that is just a very poor excuse to make changes that would make the reliable work *impossible* for others who use it *correctly*. And then - the proposed change makes it *impossible* to apply formatting changes *without* changing data. I suggest you to simply fork LibreOffice, make the changes you want, and advertise it as the new shiny fork with this great new feature, which would surely simply make all users switch, that way voting by feet. Job done. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 98590] Confusing behavior when cell with number is changed to format Text: no indication if cell value type is number or text
https://bugs.documentfoundation.org/show_bug.cgi?id=98590 --- Comment #13 from b. --- @Mike Kaganski, let's say there are two options, A - immediate reaction on cell format change, with a chance for the user to see that his changes have been 'accepted', 'worked', and in case of an error to see it immediately (not sure, but have a chance) and to assign it correctly to the cause, and to remove it with a simple ctrl-z and to continue working with undamaged data, and B: where the user's changes are not processed at first, so he thinks 'it didn't work' and 'blindly' throws other changes behind that make everything worse, only to be surprised months or years later by changes or unwanted consequences of changes he can't assign, maybe didn't even make himself, and can only correct with tedious debugging, with a good chance of stepping on other landmines he or other people have installed before or in between? i know that you think the second way is better, IMHO it's stupid and i regret that both the work in the sheet and the code of calc are developing more and more in this direction. i see one argument for option B: excel doe's it that way. but as already mentioned more than once, even if you follow an elephant, you don't have to go along with all the nonsense it spouts. To keep compatibility: two options, 'reasonable calculations' and 'Excel compatibility mode'. i suggest to let the users vote how hey would like to have it instead of 'experts' making stubborn decisions and forcing them on the users. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142408] [DOCX] vert="vert270" is handled as vert="vert"
https://bugs.documentfoundation.org/show_bug.cgi?id=142408 Valek Filippov changed: What|Removed |Added Keywords||filter:docx -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142409] New: Created letterhead template in Libre Office Writer, client uses MS 365 for Mac and can't type in it
https://bugs.documentfoundation.org/show_bug.cgi?id=142409 Bug ID: 142409 Summary: Created letterhead template in Libre Office Writer, client uses MS 365 for Mac and can't type in it Product: LibreOffice Version: 6.4.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lisa.visiblyme...@gmail.com I created a letterhead template in Writer and saved to a .docx and .dotx format for my client. I didn't know the client uses Apple/Mac, new this year and likely on MS Office 365 for Mac. They can't type in the document - how do I save it for their use? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142390] calc 7.2.0.0.a0+ >2021-05-19, no mouse cursor in cell area
https://bugs.documentfoundation.org/show_bug.cgi?id=142390 --- Comment #15 from Timur --- Discussion on cursor is in bug 104169 , here is it missing in Windows. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 137173] Fileopen: DOC with hyperlinks hangs
https://bugs.documentfoundation.org/show_bug.cgi?id=137173 --- Comment #6 from Timur --- DOC can be loaded in 43all oldest, so bibisect: commit a7a51689878f5428c3934558f820fb65af04fedb Date: Sun Dec 9 16:52:12 2012 + source-hash-2a360b68475d6fff5b6618feddb0b52f3a4a2373 previous source-hash-699e7d9e4081942bb0ad73e9be73f90a26d0c2f7 https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=699e7d9e4081942bb0ad73e9be73f90a26d0c2f7..2a360b68475d6fff5b6618feddb0b52f3a4a2373 Many commits here. And I'm not even sure it's correct, because loading previous bibisect commit once worked, once not. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 137173] Fileopen: DOC with hyperlinks hangs
https://bugs.documentfoundation.org/show_bug.cgi?id=137173 Timur changed: What|Removed |Added Summary|Document with hyperlinks|Fileopen: DOC with |hangs |hyperlinks hangs Keywords|bibisectRequest |bibisected --- Comment #5 from Timur --- Can be loaded in 43all oldest, so: commit a7a51689878f5428c3934558f820fb65af04fedb Date: Sun Dec 9 16:52:12 2012 + source-hash-2a360b68475d6fff5b6618feddb0b52f3a4a2373 previous source-hash-699e7d9e4081942bb0ad73e9be73f90a26d0c2f7 Author: Noel Grandin AuthorDate: Tue Jun 12 15:41:27 2012 +0200 Commit: Michael Stahl CommitDate: Tue Jun 12 23:25:10 2012 +0200 Convert SV_DECL_PTRARR(SvBaseLinks) to std::vector Change-Id: I9197dc4fd7ed32f030de8121913265ec78c83585 https://cgit.freedesktop.org/libreoffice/core/log/?qt=range=699e7d9e4081942bb0ad73e9be73f90a26d0c2f7..2a360b68475d6fff5b6618feddb0b52f3a4a2373 Many commits here. And I'm not even sure it's correct, because loading previous bibisect commit once worked, once not. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 142390] calc 7.2.0.0.a0+ >2021-05-19, no mouse cursor in cell area
https://bugs.documentfoundation.org/show_bug.cgi?id=142390 --- Comment #14 from b. --- have seen the fatcross cursor in linux ... not a good idea (IMHO), ugly, and covers the details one wants to see to click onto the right point, highlighting the cursor in general is a good idea, esp. for modern LCD or TFT displays or videos where people should follow a cursor with their eyes which they don't have in own control (if you lead the mouse yourself you can get the focus back because you know what your hand is doing, watching videos this feature fails), but other appliances use better options for that, e.g. a transparent neon spraypaint-point moving together with the original 'sharp pointing' cursor, -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
