[Libreoffice-bugs] [Bug 124852] Heading characters much too big when copy-paste as GDI metafile
https://bugs.documentfoundation.org/show_bug.cgi?id=124852 --- Comment #5 from Rainer Bielefeld Retired --- Still the same like 2019-04-20 13:59:58 UTC with Server Installation of Version: 7.6.0.0.alpha0+ (X86_64) Build ID: 3bc7cc14706f47d740dfc5715970054922ca470c CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE; Theme: Automatic (Colibre) Calc: CL threaded – Special new User Profile for testing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133206] UI: Closing a style dialog by pressing OK changes the focus in the styles sidebar to the active style where the cursor stands
https://bugs.documentfoundation.org/show_bug.cgi?id=133206 --- Comment #18 from BogdanB --- And with edit and OK is going to Default Style. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133206] UI: Closing a style dialog by pressing OK changes the focus in the styles sidebar to the active style where the cursor stands
https://bugs.documentfoundation.org/show_bug.cgi?id=133206 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #17 from BogdanB --- Created attachment 187598 --> https://bugs.documentfoundation.org/attachment.cgi?id=187598=edit video testing the bug In 7.6 is moving the double-clicked style to the top. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115903] Adding paragraphs in a (multi-page) table with embedded tables is slow and cpu hogging
https://bugs.documentfoundation.org/show_bug.cgi?id=115903 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #6 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155553] Crash in: SfxItemSet::~SfxItemSet()
https://bugs.documentfoundation.org/show_bug.cgi?id=13 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155552] Just trying to ask a question
https://bugs.documentfoundation.org/show_bug.cgi?id=12 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Sorry, but this is not the place. Please use our forum https://ask.libreoffice.org/c/english/5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155553] Crash in: SfxItemSet::~SfxItemSet()
https://bugs.documentfoundation.org/show_bug.cgi?id=13 Carl changed: What|Removed |Added Version|7.4.1.2 release |7.5.3.2 release --- Comment #1 from Carl --- Turns out I had upgraded to v7.5.3.2, I'm not sure why my initial post defaulted to 7.4..., but I have now corrected the version field. I am also not sure if this is related to my previous bug report, number 152477. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155553] New: Crash in: SfxItemSet::~SfxItemSet()
https://bugs.documentfoundation.org/show_bug.cgi?id=13 Bug ID: 13 Summary: Crash in: SfxItemSet::~SfxItemSet() Product: LibreOffice Version: 7.4.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ckru...@bellsouth.net This bug was filed from the crash reporting server and is br-c8ec52b0-fb30-4eb3-87a7-4ff79ae9f572. = I have a couple spreadsheets I use to collect and summarize GPS, heart rate, speed, etc. data from bicycle rides. One spreadsheet is where I copy & paste large chunks of raw data from a csv file, (typically 8000-ish rows of 8 columns) summarize and chart each ride, one tab per ride. The other sheet tracks all the rides, and I manually copy the summarized data from the first, except for a "notes" field, in which I copy & paste a single cell of unformatted text. Everything works as it should, no files have been compromised. But... Typically I close the all-rides summary file first, then the daily data file. When I close the dailies one I get the pop-up saying LO has crashed, and the following files will be restored, but there are no files listed. I filed the Crash Report this time, but this time I am actually following up on it like I'm supposed to... My files are fine, and open on other machines with no issues. I also just noticed I seem to still be running a 7.4... release, I thought I had already put 7.5 on this machine, I will do that and update this if the problem persists. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105753] The setting "Mirror on even pages" for frames is misbehaving
https://bugs.documentfoundation.org/show_bug.cgi?id=105753 BogdanB changed: What|Removed |Added Blocks||107656 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107656 [Bug 107656] [META] Frame bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107656] [META] Frame bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107656 BogdanB changed: What|Removed |Added Depends on||105753 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105753 [Bug 105753] The setting "Mirror on even pages" for frames is misbehaving -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147123] FILEOPEN ODT: Image has a different position on file open since 7.3 or 7.4 (comment 3)
https://bugs.documentfoundation.org/show_bug.cgi?id=147123 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||103152 --- Comment #5 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 BogdanB changed: What|Removed |Added Depends on||147123 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=147123 [Bug 147123] FILEOPEN ODT: Image has a different position on file open since 7.3 or 7.4 (comment 3) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130570] Make auto-increment on copied numbers configurable
https://bugs.documentfoundation.org/show_bug.cgi?id=130570 BogdanB changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113499] [META] AutoFill bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113499 BogdanB changed: What|Removed |Added Depends on||130570 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=130570 [Bug 130570] Make auto-increment on copied numbers configurable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130570] Make auto-increment on copied numbers configurable
https://bugs.documentfoundation.org/show_bug.cgi?id=130570 BogdanB changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Summary|Autoinput can not be turned |Make auto-increment on |off |copied numbers configurable CC||buzea.bog...@libreoffice.or ||g Blocks||113499 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113499 [Bug 113499] [META] AutoFill bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155318] logical operator for conditional section hiding
https://bugs.documentfoundation.org/show_bug.cgi?id=155318 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155537] MCGR FILESAVE OOXML Combining Color and Transparent Gradient could be smarter
https://bugs.documentfoundation.org/show_bug.cgi?id=155537 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155367] Submit form to email address does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=155367 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155312] Libreoffice and Webdav behind HAProxy
https://bugs.documentfoundation.org/show_bug.cgi?id=155312 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155315] Auto-correction should not apply when multiple correct forms are possible
https://bugs.documentfoundation.org/show_bug.cgi?id=155315 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155297] FILEOPEN DOCX loading loses paragraph properties, including justification and line spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=155297 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155262] LibreOffice crashes in server mode with "free(): corrupted unsorted chunks"
https://bugs.documentfoundation.org/show_bug.cgi?id=155262 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155367] Submit form to email address does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=155367 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155243] EDITING: keyboard, or most combinations, are dead when document opens. And no blinking cursor in writer. But there are ways to get around.
https://bugs.documentfoundation.org/show_bug.cgi?id=155243 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155262] LibreOffice crashes in server mode with "free(): corrupted unsorted chunks"
https://bugs.documentfoundation.org/show_bug.cgi?id=155262 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155243] EDITING: keyboard, or most combinations, are dead when document opens. And no blinking cursor in writer. But there are ways to get around.
https://bugs.documentfoundation.org/show_bug.cgi?id=155243 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151813] Can't open app after installing update
https://bugs.documentfoundation.org/show_bug.cgi?id=151813 --- Comment #3 from QA Administrators --- Dear gcandera, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152326] wrong month sort in pivot table
https://bugs.documentfoundation.org/show_bug.cgi?id=152326 --- Comment #2 from QA Administrators --- Dear John Hopkins, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152063] version 7.4.2 update won't run after installation
https://bugs.documentfoundation.org/show_bug.cgi?id=152063 --- Comment #3 from QA Administrators --- Dear shearist, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152164] Use the same background and style for content control and other fields' placeholder text
https://bugs.documentfoundation.org/show_bug.cgi?id=152164 --- Comment #7 from QA Administrators --- Dear Hossein, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149684] converting .docx to .pdf - but not all pages and also two pages merged into same page in pdf
https://bugs.documentfoundation.org/show_bug.cgi?id=149684 --- Comment #6 from QA Administrators --- Dear prasadgsk, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146461] LibreOffice Spreadsheet crash when clicking and dragging over formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=146461 --- Comment #19 from QA Administrators --- Dear Ken, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140156] Significant slow-down when entering two languages in the line
https://bugs.documentfoundation.org/show_bug.cgi?id=140156 --- Comment #5 from QA Administrators --- Dear elya.wygoda, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72515] Grammar warning messages use document language instead of UI language
https://bugs.documentfoundation.org/show_bug.cgi?id=72515 --- Comment #12 from QA Administrators --- Dear Pedro, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142534] Writer dictionary error (?).
https://bugs.documentfoundation.org/show_bug.cgi?id=142534 --- Comment #2 from QA Administrators --- Dear gsanchioni, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142297] gnumeric file is not opened correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=142297 --- Comment #10 from QA Administrators --- Dear Valek Filippov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113431] Font name is not kept when copying from Calc to Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=113431 --- Comment #7 from QA Administrators --- Dear Ole Tange, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 115886] missing slide borders in "slide sorter" view on hiDPI display
https://bugs.documentfoundation.org/show_bug.cgi?id=115886 --- Comment #9 from QA Administrators --- Dear Eric M, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124852] Heading characters much too big when copy-paste as GDI metafile
https://bugs.documentfoundation.org/show_bug.cgi?id=124852 --- Comment #4 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114574] FILEOPEN PDF Import: Sheet music breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=114574 --- Comment #12 from QA Administrators --- Dear Robert Pollak, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104261] VIEWING: Calc red comment indicator is changing shape
https://bugs.documentfoundation.org/show_bug.cgi?id=104261 --- Comment #10 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155552] New: Just trying to ask a question
https://bugs.documentfoundation.org/show_bug.cgi?id=12 Bug ID: 12 Summary: Just trying to ask a question Product: LibreOffice Version: 3.3.0 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ao.techn...@protonmail.com Description: Does LibreOffice have some thing like microsoft's Visio? If not, is there something planned for it in the future? I would have sent this in through other means but the website does not have a contact link or email, so I ended up here. Steps to Reproduce: 1.n/a 2.n/a 3.n/a Actual Results: Just read the question Expected Results: Just an answer Reproducible: Always User Profile Reset: Yes Additional Info: n/a -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155551] Open interval vs “fixed” interval for index/match or lookup function
https://bugs.documentfoundation.org/show_bug.cgi?id=11 --- Comment #4 from ady --- (In reply to m.a.riosv from comment #2) > Looks that TRIM() doesn't shortcut for reference to the whole column A:A. > I think many text functions e.g., SUBSTITUTE has the same issue. Having TRIM() operating at least 123*128 = 15744 times is not the same as operating 123 times only. Here is what I mean: 1. In attachment 187596 from comment 1, worksheet "Pivot_stock_1", cell C2: =TRIM(A2) and copy down until C124. 2. In worksheet ledger, cell B2: =INDEX($Pivot_stock_1.B:B;MATCH(A2;$Pivot_stock_1.C:C;0)) 3. In worksheet ledger, cell D2: =INDEX(Pivot_stock_1.$B$2:$B$124;MATCH(A2;Pivot_stock_1.$C$2:$C$124;0)) 4. Copy B2:E2 down until B129:E129. With that, TRIM() will be operating 123 times (only), while the INDEX() and MATCH() functions will operate the same amount of times as before. In my system, this change generates a much faster response, which might suggest that the problem might not be "Open interval vs “fixed” interval for index/match or lookup function" (as the current title/subject suggests), but rather that the TRIM() function (operating on strings) is taking most of the resources. If that is correct (which needs to be corroborated by developers), then the subject of this report (at the time I am writing this) is not adequate/relevant. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155551] Open interval vs “fixed” interval for index/match or lookup function
https://bugs.documentfoundation.org/show_bug.cgi?id=11 --- Comment #3 from m.a.riosv --- Please change the title accordantly. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155537] MCGR FILESAVE OOXML Combining Color and Transparent Gradient could be smarter
https://bugs.documentfoundation.org/show_bug.cgi?id=155537 m.a.riosv 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] [Bug 155537] MCGR FILESAVE OOXML Combining Color and Transparent Gradient could be smarter
https://bugs.documentfoundation.org/show_bug.cgi?id=155537 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Created attachment 187597 --> https://bugs.documentfoundation.org/attachment.cgi?id=187597=edit Screenshot 7.5 vs 7.6 odt, 7.5 docx vs 7.6 docx word Reproducible Version: 7.5.4.1 (X86_64) / LibreOffice Community Build ID: 3a6a10a8a824826630ea908dcaea93b45a6a0af1 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 20873f073ae4a9478f0a84355f779a2176bd2ec8 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155551] Open interval vs “fixed” interval for index/match or lookup function
https://bugs.documentfoundation.org/show_bug.cgi?id=11 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Looks that TRIM() doesn't shortcut for reference to the whole column A:A. I think many text functions e.g., SUBSTITUTE has the same issue. Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 20873f073ae4a9478f0a84355f779a2176bd2ec8 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96579] [WRITER] Figure caption badly converted in Word format because image anchoring and wrapping is changed to as-character/DML
https://bugs.documentfoundation.org/show_bug.cgi?id=96579 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=44 ||158 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88171] [META] Binary DOC format limitations
https://bugs.documentfoundation.org/show_bug.cgi?id=88171 Justin L changed: What|Removed |Added Depends on||44158 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=44158 [Bug 44158] FORMATTING or FILE SAVE - .odt file (containing frames) saved as .doc opens in Word incorrectly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 44158] FORMATTING or FILE SAVE - .odt file (containing frames) saved as .doc opens in Word incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=44158 Justin L changed: What|Removed |Added Blocks||88171 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=96 ||579 --- Comment #10 from Justin L --- repro 7.6+ In this comment I am going to focus on the Lions picture on the right, anchored "to paragraph" inside another frame and positioned according to the entire paragraph area. On saving to DOC format, it changes to as-character anchor - and of course is completely misplaced. This was already true in OOo 3.3. Changing a "to paragraph" anchor to an "as character" anchor doesn't seem to make sense. But we have in wrtw8nds.cxx aFlyFrame.ForceTreatAsInline(); and if that is ignored, then the image is lost. Well, that helps to make sense of what I saw in MS Word. When looking at the properties of that inline picture, I couldn't do anything about the layout - all the settings were grayed out. If I copy and paste that picture into the frame again, it still has no positioning. But if I paste into the body text, then the positioning is available. So it really is true, DOC format doesn't allow a floating image inside of a frame. There is basically NOTHING we can do to fix this. [Changing the anchor to to-page isn't a great idea because the contents might flow differently, and thus put the image on a different page.] This is a DOC format limitation. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=88171 [Bug 88171] [META] Binary DOC format limitations -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 88171] [META] Binary DOC format limitations
https://bugs.documentfoundation.org/show_bug.cgi?id=88171 Justin L changed: What|Removed |Added Depends on|55528 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=55528 [Bug 55528] FILESAVE: 100% table width not saved in doc file as relative -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155243] EDITING: keyboard, or most combinations, are dead when document opens. And no blinking cursor in writer. But there are ways to get around.
https://bugs.documentfoundation.org/show_bug.cgi?id=155243 --- Comment #3 from u...@net9.ga --- My understanding is that I should have a blinking cursor when I open a writer document. And not having such a cursor is a bug. I 1. Closed any the LibreOffice application I had open. 2. Used the [Quick test for corrupted profiles: use a temporary, new user profile](https://wiki.documentfoundation.org/UserProfile) soffice -env:UserInstallation=file:///tmp/test The terminal had javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx and I got LibreOffice welcome screen. 3. File -> New -> Text Document gave me a writer screen, with a blinking cursor, and a tip of the day. I confirmed, OK, the tip. Blinking cursor still on the empty document. There was also a message, with a blue background before the empty document, I am using LibreOffice 7.5 for the first time. Would I like to learn what's new? 4. I inserted the letter a in the empty document, and exited LibreOffice, saving a.odt to /tmp/. I then noticed there is also a terminal message (soffice:21828): Gtk-WARNING **: 22:47:10.191: Could not init tracker3 search engine: The name org.freedesktop.Tracker3.Miner.Files was not provided by any .service files 5. Next I rerun soffice -env:UserInstallation=file:///tmp/test. Got, again javaldx: Could not find a Java Runtime Environment! Warning: failed to read path from javaldx and a LibreOffice opening screen, suggesting a small screen shot of the a document. 6. By clicking the a document small screen shot with the mouse, I got it opened. Without a blinking cursor. The alt+letter keystroke did opened the suitable menu. In the Edit menu, the Find... was grayed. But I still had no blinking cursor at the body of the document. As usual, I had to click the mouse in order to get the blinking cursor. As for other applications from the LibreOffice suite, I am only actually using calc. I am not sure what is the expected calc behavior. Doing a similar test with a new spreadsheet, the A1 cell has blue borders, but no blinking cursor can be seen. Inserting a at A1 and exiting by saving /tmp/a.ods. Not sure If I had to somehow re-select the A1 cell before I could insert a into it. Rerunning LibreOffic now has a small screen shots of a.ods and a.odt. Choosing a.ods open it. The A1 cell has blue borders, but no cell is active. Striking the keyboard b key does not seem to do something. That looks to me similar broken behavior on the side of calc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 V Stuart Foote changed: What|Removed |Added CC||kha...@libreoffice.org, ||vsfo...@libreoffice.org --- Comment #14 from V Stuart Foote --- @Khaled, could this be a Harfbuzz composition issue? What width for a space is used for composing line wrap position a line of text against document/paragraph margins? Tabs are not similarly affected--just strings of characters. In addition to STR here, instead working in a two-column page, string of spaces pass completely out of the column, over the adjacent column, and off the page--seemingly with no line wrap. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155551] Open interval vs “fixed” interval for index/match or lookup function
https://bugs.documentfoundation.org/show_bug.cgi?id=11 --- Comment #1 from Gisseh --- Created attachment 187596 --> https://bugs.documentfoundation.org/attachment.cgi?id=187596=edit example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155551] New: Open interval vs “fixed” interval for index/match or lookup function
https://bugs.documentfoundation.org/show_bug.cgi?id=11 Bug ID: 11 Summary: Open interval vs “fixed” interval for index/match or lookup function Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gis...@protonmail.com Description: Dear all, I’d like to report a particular “buggy” behavior from LO Calc that I do not see on other spreadsheet programs, such MS Excel, WPS, Google sheets. When we use a text funcion such a match/index or even vlookup with an “open interval” (e.g. B:B instead of $B$2:$B$129$), and I copy it to multiple lines, LO Calc seems to look through the “infinite” lines and therefore becoming unresponsive, and the calculation really takes very long to be completed. In my daily basis I use the match/index function to make stock / sales / product information sheets to speak to each other, and this LO behavior is quite annoying as to achieve a good performance I have to fixate all the intervals, where I’m used to just inform the column label on other spreadsheets software. I am using the attached spreadsheet as an example (this is a real example from my job). I prepared two example columns, where we can copy the formula from D2 to D129 on the ledger tab, and this would just work with good performance (it calculates within a second). If we do the same from B2 to B129, it will also calculate correctly, however it takes around a minute on my laptop, and the Operationa System thinks the software has crashed. Am I missing something here, or this is something we could report as a bug / improvement to be done? Thank you all for your time. The best, PS: Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: pt-BR (pt_BR.UTF-8); UI: pt-BR Flatpak Calc: threaded I uploaded an example file at: https://ask.libreoffice.org/t/open-interval-vs-fixed-interval-for-index-match-or-vlookup/91992 Steps to Reproduce: 1. Create a with single entries containing spaces after it and one attribute to it, e.g. Reference "A ", description X 2. In another tab, spread some different references, A, B, C etc 3. Use a match/index to search descriptions such X as a Match of trimmed A etc Actual Results: If we use a trim function and do not fix the lookup interval, CALC seems to search on the entire number of lines, taking too much time and sometimes crashing Expected Results: Work with equivalent performance as with the "trim" function Reproducible: Always User Profile Reset: No Additional Info: I uploaded an example file at: https://ask.libreoffice.org/t/open-interval-vs-fixed-interval-for-index-match-or-vlookup/91992 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124615] FILESAVE AND FILEOPEN: rotated images not rotated on import or export
https://bugs.documentfoundation.org/show_bug.cgi?id=124615 --- Comment #7 from Justin L --- Created attachment 187595 --> https://bugs.documentfoundation.org/attachment.cgi?id=187595=edit 124615_dump.doc: doc_dump of RotatedPenguin.doc A brief search in the documentation and the doc dump didn't indicate what the sprm name that specifies the rotation. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146976] Writer Crashes After Opening A Large File of 2000 text pages
https://bugs.documentfoundation.org/show_bug.cgi?id=146976 --- Comment #14 from csyu@gmail.com --- @Caolán McNamara it doesn't crash in the latest version of Libreoffice. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 56026] FORMATTING: page header is abnormal in DOC (OK if resaved in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=56026 --- Comment #12 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155494] Cursor goes beyond margins when typing spaces at the end of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=155494 --- Comment #13 from William Friedman --- Thank you, Attila, for the detailed response. I have never used MS Word in any sustained way (or, for that matter, in any occasional way), so I can't speak to their design choices. In one of the threads I read related to this matter, someone made a general point about how LO shouldn't merely mimic Word when Word's implementation of something is bad. I agree with that point, and if this is indeed how Word handles extra spaces entered at the end of the line, then I think Word's implementation is bad, too. I want to address what you wrote here: "we want to be able to hit more spaces, but we want to see as there would be no spaces there .. some cases we want to be able to move into it.. some cases we don't.. we dont want to break line because of them.. but if you put 1 letter in the middle, then suddenly show the spoaces at next line, and change its behaviour..." My first question is *why* "we want to be able to hit more spaces, but we want to see as there would be no spaces there." Why *not* treat spaces entered at the end of the line exactly as any other text character, wrapping to the next line and inserting spaces just as if someone typed a long string of "a"s or whatever? Until I can understand why anyone would "want to see as there would be no spaces there" I can't really relate to the controversy. The fact that spaces are not shown until a letter is inserted, which "change[s] its behaviour" seems like argument enough that not displaying and treating spaces at the end of lines as regular characters is a poor choice. My simple feature request, then, would be to treat spaces like any other text character, that they wrap to the next line and continue to be inserted at the margin. I hope you or someone else can explain why this solution would be bad or negatively affect use cases that I can't currently think of. Whether or not my suggestion is wrongheaded or naive, I think the current implementation is worse than the old implementation where extra end-of-line spaces would simply move the cursor to the beginning of the next line and not display the added spaces. Beyond the bizarre visual artifact of going beyond the margin -- which, if more spaces are added, continues until the cursor itself is no longer visible, this implementation causes problems in Tables (and, I imagine, multi-column pages) when spaces cause the cursor to appear in the next cell, despite still changing the original cell. The implementation is also problematic because selecting the entire line with spaces that go beyond the margin only visually selects until the margin, even though the extra spaces are selected as well. In addition, try the following steps, which initially drew my attention to this issue: 1. Right justify LTR text. 2. Type spaces at the end of the line (or a line of spaces). 3. Notice that the cursor disappears entirely, rather than going beyond the line. I hope these issues will at least push for a reconsideration of this new implementation, and at best, lead to accepting my suggestion that spaces be treated as ordinary characters. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38779] Position of text boxes not retained when opening MS Office .doc files FORMATTING problem
https://bugs.documentfoundation.org/show_bug.cgi?id=38779 --- Comment #22 from Justin L --- Using MS Word 2010, I saved as DOCX (LO opens that fine). Then I used MS Word to save the DOCX back to DOC. It alerted me that it needed to convert frame stuff to "something suitable" for DOC, and LO opens that one fine. Using the minimum version, I see the same curious thing as comment 20 - it is fine in OOo 3.3, but in the first LO 3.3 it is aligned to page, not paragraph. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155548] VLOOKUP and MATCH - random results
https://bugs.documentfoundation.org/show_bug.cgi?id=155548 --- Comment #3 from ady --- Problem not seen in 7.3. Please test with 7.4.7. Possibly solved by patch posted for bug 151958 comment 21. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146827] Glyph wiggle when link gets converted to field
https://bugs.documentfoundation.org/show_bug.cgi?id=146827 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #4 from BogdanB --- Repro in 7.6. Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 BogdanB changed: What|Removed |Added Depends on||135156 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=135156 [Bug 135156] Text splitting bit arbitrary for ODT/RTF/DOC fine for DOCX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135156] Text splitting bit arbitrary for ODT/RTF/DOC fine for DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=135156 BogdanB changed: What|Removed |Added Blocks||87740 CC||buzea.bog...@libreoffice.or ||g --- Comment #6 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87740 [Bug 87740] [META] Anchor and text wrapping bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125342] Excel 5.0/95 XLS File shows messy code in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=125342 BogdanB changed: What|Removed |Added Status|NEW |RESOLVED CC||buzea.bog...@libreoffice.or ||g Resolution|--- |WORKSFORME --- Comment #8 from BogdanB --- Everything is fine now. Tested with Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: fc4f7db59152f606b6aa88cf32197700959d0f8b CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Please retest with 7.6, and if you can reproduce this bug, please change the status to New. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154996] Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=154996 --- Comment #10 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/3ffbf68223b981335abdfede5dc5f86c30269c13 tdf#154996 Add tabbed UI commands in Help page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38779] Position of text boxes not retained when opening MS Office .doc files FORMATTING problem
https://bugs.documentfoundation.org/show_bug.cgi?id=38779 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #21 from Justin L --- Created attachment 187594 --> https://bugs.documentfoundation.org/attachment.cgi?id=187594=edit 38779_min.doc: minimal example - should be 1cm from paragraph, not 1cm from page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103757] FILESAVE, FORMATTING: Overflow error for column width and row height
https://bugs.documentfoundation.org/show_bug.cgi?id=103757 ady changed: What|Removed |Added Summary|FILESAVE, FORMATTING: |FILESAVE, FORMATTING: |Different limits for|Overflow error for column |column/row size in UI and |width and row height |filters | --- Comment #7 from ady --- The way this report is presented, it would seem as if some generic behavior is incorrect, whichever the values. But this is not the case. The inconsistency, if we could call it this way, is only seen when the values are higher than some limit. When the value for cell's height or width is greater than some supported maximum, the value that is saved is not fixed to such maximum, but rather to some kind of overflow. Example: * column width or row height set to 650mm > saved as 649.99 mm, OK. * column width or row height set to 660mm > saved as 4.62mm, KO. * column width or row height set to 670mm > saved as 14.64mm, KO. In each case, set the value, save the file, reload the file; then check the value again. So, whether with or without some real limit to row height and/or column width values (IDK whether there are), there is some kind of overflow error when saving the values. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100805] FILEOPEN Image shows on a different page cause by different page wrapping caused by difference in ..
https://bugs.documentfoundation.org/show_bug.cgi?id=100805 Justin L changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEW |RESOLVED --- Comment #15 from Justin L --- repro 7.6+ This is an "every TWIP counts" kind of bug report. As such, it adds no value whatsoever. Closing because it is basically inactionable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112702] [META] DOC (binary) header and footer-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112702 Bug 112702 depends on bug 100805, which changed state. Bug 100805 Summary: FILEOPEN Image shows on a different page cause by different page wrapping caused by difference in .. https://bugs.documentfoundation.org/show_bug.cgi?id=100805 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112701] [META] DOC (binary) image-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=112701 Bug 112701 depends on bug 100805, which changed state. Bug 100805 Summary: FILEOPEN Image shows on a different page cause by different page wrapping caused by difference in .. https://bugs.documentfoundation.org/show_bug.cgi?id=100805 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100844] FILEOPEN DOC Image outline seems blue instead of black because (blue) area is shown inside double border and around border
https://bugs.documentfoundation.org/show_bug.cgi?id=100844 --- Comment #8 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143383] FILEOPEN DOC: wrap is tight in Writer but not in Word
https://bugs.documentfoundation.org/show_bug.cgi?id=143383 --- Comment #3 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112984] Invisible shapes in doc
https://bugs.documentfoundation.org/show_bug.cgi?id=112984 Justin L changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||2866 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142866] Many arrows from gallery are invisible when saved to .doc
https://bugs.documentfoundation.org/show_bug.cgi?id=142866 Justin L changed: What|Removed |Added Hardware|x86-64 (AMD64) |All See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||2984 --- Comment #7 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142983] Shape from gallery saved to .doc is malformed
https://bugs.documentfoundation.org/show_bug.cgi?id=142983 Justin L changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Version|7.0.6.2 release |Inherited From OOo --- Comment #6 from Justin L --- repro 7.6+ It looked similar in OOo 3.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41419] Exporting a drawing (grouped shapes) from writer to Word .doc breaks the drawing
https://bugs.documentfoundation.org/show_bug.cgi?id=41419 Justin L changed: What|Removed |Added Priority|high|low Severity|major |minor --- Comment #25 from Justin L --- repro 7.6+ But exporting a group of shapes while changing to a completely different format is definitely not high priority. In fact, it is about as low priority as I can imagine. Much higher priority is actually simply importing DOC shapes properly. We have a ton of bug reports that can't even import or round-trip yet. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 112984] Invisible shapes in doc
https://bugs.documentfoundation.org/show_bug.cgi?id=112984 --- Comment #11 from Justin L --- Created attachment 187593 --> https://bugs.documentfoundation.org/attachment.cgi?id=187593=edit 112984_min.doc: I assume this is just a type of shape we don't have an import filter for repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152
Bug 103152 depends on bug 151833, which changed state.
Bug 151833 Summary: IMAGE SIZE: Freeze/hang after changing height to 75%
relative ("keep ratio" checked
https://bugs.documentfoundation.org/show_bug.cgi?id=151833
What|Removed |Added
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151833] IMAGE SIZE: Freeze/hang after changing height to 75% relative ("keep ratio" checked
https://bugs.documentfoundation.org/show_bug.cgi?id=151833 Gabor Kelemen (allotropia) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED CC||kelem...@ubuntu.com --- Comment #15 from Gabor Kelemen (allotropia) --- I can't reproduce the loop in current master since: https://git.libreoffice.org/core/commit/c8cb7a658b33e296024044f3377378644a9a97ef tdf#144494 sw: fix layout loop *** This bug has been marked as a duplicate of bug 144494 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 64095] Fileopen DOC: Writer misplaces Text Frame and Shape (so looks as DOCX in MSO)
https://bugs.documentfoundation.org/show_bug.cgi?id=64095 --- Comment #16 from Justin L --- repro 7.6+ An AS-CHAR drawing canvas overlaps with a frame in MSO, but in LO it wraps (down) because it doesn't fit. Complicated by right-to-left I imagine. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120853] [META] DOC (binary) document protection-related issues/enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=120853 Justin L changed: What|Removed |Added Depends on||59199 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=59199 [Bug 59199] EDITING: protected footer in .doc is editable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 59199] EDITING: protected footer in .doc is editable
https://bugs.documentfoundation.org/show_bug.cgi?id=59199 Justin L changed: What|Removed |Added Blocks||120853 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120853 [Bug 120853] [META] DOC (binary) document protection-related issues/enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 130005] EDITING: Shift+Ctl+S does not work as advertised in Search
https://bugs.documentfoundation.org/show_bug.cgi?id=130005 --- Comment #8 from Adalbert Hanßen --- (In reply to Caolán McNamara from comment #5) > ctrl+shift+s works for me in gtk3 in e.g. the find and replace dialog, to > show the insert special character dialog. At least since issue #142706 done > in 2021 which is newer than comments 1-3 so this sounds like a duplicate of > #142706 > > On the other hand comment #4 is about a contemporary version which should > have the fix (signalEntryInsertSpecialCharKeyPress in > vcl/unx/gtk3/gtkinst.cxx) in it Today I looked into this one again. The problem seems to have been resolved by allowing to introduce things like currency characters, greek characters, EN_DASH and other characters not directly on the keyboard. I misunderstood the original trick. I was looking for something which lets me replace paragraph marks by forced feedbacks, or tabs by something else which I have defined. Microsoft Word has something similar, but I don't recall their exact syntax, perhaps it was ^p, ^n and so on I (which is also quite ununsual). There is an extension AltSearch 1.4.2.oxt which lets one replace paragraph marks by forced feedbacks and so on. Unfortunately AltSearch has some bugs and it looks like not being supported any longer. In 2011 Timur started a never ending discussion on the usability of Find and Replace in LibreOffice (https://bugs.documentfoundation.org/show_bug.cgi?id=38261). In comment 11 on this topic, Jax has already complained about AltSearch's features and bugs. In comment 20 I supported his view referring to similar request in OpenOffice from 2003 (happy birthday, it's mature now) and I reminded, that a "batch" feature assigning a name to such a storable replacement rule like in AltSearch must not be forgotten, since writing good regular expressions is not an easy task. In comment 25 to that thread I discussed the important features to be incorporated into LO Writer's native Search But this discussion was not in vain, because Shift-Ctl-S provides another property that has not been considered in the other discussions. So you can't lose that either. In AltSearch version 1.4.2 Shift-Ctl-S works by the way! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 74498] FILEOPEN DOC:Misplaced draw-textboxes in drawing canvas (frame in frame anchors) brochure
https://bugs.documentfoundation.org/show_bug.cgi?id=74498 Justin L changed: What|Removed |Added Hardware|x86 (IA32) |All Whiteboard|target:7.3.0| OS|Windows (All) |All Summary|Misplaced images (frames, |FILEOPEN DOC:Misplaced |...) in particular Office |draw-textboxes in drawing |.doc - Working with Office, |canvas (frame in frame |KingsoftWriter |anchors) brochure --- Comment #11 from Justin L --- repro 7.6+ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 51729] EDITING: Previously copied cells are incorrectly highlighted as still in clipboard after no longer in clipboard
https://bugs.documentfoundation.org/show_bug.cgi?id=51729 ady changed: What|Removed |Added Summary|EDITING: Copied cells are |EDITING: Previously copied |incorectly highlighted as |cells are incorrectly |copied after next copying |highlighted as still in |to the clipboard|clipboard after no longer ||in clipboard --- Comment #11 from ady --- Still repro as of 7.6.alpha. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122715] FILEOPEN XLSB format is inconsistent with Excel with incorrect cell references and hiding
https://bugs.documentfoundation.org/show_bug.cgi?id=122715 --- Comment #8 from ady --- The Pivot Table is imported differently in Calc than in Excel. Be careful not to click on row 4, so as not modify the Pivot Table itself. Examples (cells) to compare between Excel and Calc: _ F4, Calc does not consider the column as part of the PT. _ F18 (900 <> 0) _ B18:C19 (grouped, empty vs another item) So row 18 complicates the comparison of differences, and generates the offset in the resulting sums. _ B27:C30 (Excel) vs B29:C32 (Calc) and their respective values in column F. _ B44:C45 (Excel) vs B48:C49 (Calc) and their respective values in column F. _ B54:C55 (Excel) vs B58:C59 (Calc) and their respective values in column F. _ B59 (Excel) vs B63 (Calc). Obviously that, starting from row 18, each row has different values in column F; some might coincide, but only by chance. IOW, Calc imports differently column F and row 18 in the Pivot Table, shifting the rest of the content and calculations. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132049] DOCX: Bitmap area size modifications of a shape not saved
https://bugs.documentfoundation.org/show_bug.cgi?id=132049 Aron Budea changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=15 | |3105| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108576] [META] Writer page style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108576 Bug 108576 depends on bug 145849, which changed state. Bug 145849 Summary: Ctrl+A and then Ctrl+M leads page style is changed to the default https://bugs.documentfoundation.org/show_bug.cgi?id=145849 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107318] [META] Clear formatting and clear direct formatting issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107318 Bug 107318 depends on bug 145849, which changed state. Bug 145849 Summary: Ctrl+A and then Ctrl+M leads page style is changed to the default https://bugs.documentfoundation.org/show_bug.cgi?id=145849 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 Bug 103030 depends on bug 145849, which changed state. Bug 145849 Summary: Ctrl+A and then Ctrl+M leads page style is changed to the default https://bugs.documentfoundation.org/show_bug.cgi?id=145849 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 73483] FORMATTING: "Clear direct formatting" deletes page breaks but this does not show up until file is reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=73483 BogdanB changed: What|Removed |Added CC||avtomot...@gmail.com --- Comment #18 from BogdanB --- *** Bug 145849 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145849] Ctrl+A and then Ctrl+M leads page style is changed to the default
https://bugs.documentfoundation.org/show_bug.cgi?id=145849 BogdanB changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #8 from BogdanB --- (In reply to Mike Kaganski from comment #7) > Likely a dupe of bug 73483. It is a duplicate. *** This bug has been marked as a duplicate of bug 73483 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155526] Moving average trend line equation on chart does not show period and R^2
https://bugs.documentfoundation.org/show_bug.cgi?id=155526 --- Comment #2 from Laurent Balland --- Actually, moving average trend line do not have R² nor equation. It is why these options are disabled in dialog. It should also be disabled context menu. I will have a look ASAP. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155293] Create icons for .uno:HighlightCharDF
https://bugs.documentfoundation.org/show_bug.cgi?id=155293 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from BogdanB --- An icon is needed. If we add this option to the toolbar, there is a very long description inserted: "Spotlight Character Direct Formatting". Not looking good. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104452] "Cut, add row, paste" doesn't update references
https://bugs.documentfoundation.org/show_bug.cgi?id=104452 ady changed: What|Removed |Added OS|Linux (All) |All --- Comment #12 from ady --- The problem is that Calc knows how to do "cut" and _immediately_ _one_ "paste", but does not know how to do the _same_ _exact_ "paste" if that action is not immediately after the initial "cut". Any "paste" action that is not the first and immediate action after the initial "cut" action will work as "(copy+)paste". This is also true for several (adjacent, vector) cells selected at once for pasting in the first immediate step – only the first pasted cell will have the same exact formula, whereas the others will behave as copy+paste. So, in Calc, when doing cut, insert (cells), paste, the resulting paste is not the same as cut and paste, but rather a copy and paste. And when repeating the first immediate paste after the initial cut, the result is also not the same as the first paste, but rather it works as a "copy+paste". Example: 1. A1: 100 2. B2: =A1*2 3. Cut B2. Note the surrounding "ants" around B2. 4. First immediate paste on D3. Result: =A1*2. Note the surrounding "ants" around B2. 5. Paste on E3. Paste on D4. Paste on B3. Note that the resulting formulas are equivalent to copying the initial B2 (still surrounded by "ants") and then pasting that on E3, D4 and B3 respectively. 6. Paste on A3. The behavior is exactly the same as step 5. With the current behavior, there is no alternative but to result in =#REF!2*2. In order to repeat the same formula several times in Calc, there are a couple of options: either use absolute references before cutting, or you have to cut the formula itself from within the input window formula bar. Unfortunately, in the second case the corresponding paste action(s) will only paste the formula, not the cell's format. Other spreadsheet tools might work differently. One possibility is to transform this report into a request for enhancement (or starting a new one), allowing to paste the initially cut cell multiple times "as-is", or even when other non-clipboard actions are performed in between. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155550] Text missing in DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=10 BogdanB changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||buzea.bog...@libreoffice.or ||g Summary|text in docx missing|Text missing in DOCX --- Comment #4 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: 583c3fcea50b69ca9d3cd866050c9e722a8f780b CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155550] text in docx missing
https://bugs.documentfoundation.org/show_bug.cgi?id=10 raal changed: What|Removed |Added Regression By||Regényi Balázs Keywords||bibisected, bisected, ||regression CC||libreoff...@nisz.hu, ||regenyi.balazs+libreoffice_ ||bugzi...@gmail.com --- Comment #3 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-7.1. Adding Cc: to Regényi Balázs ; Could you possibly take a look at this one? Thanks d95be6d4bc0034d82846136743bc4a67d619a8dc is the first bad commit commit d95be6d4bc0034d82846136743bc4a67d619a8dc Author: Jenkins Build User Date: Thu Dec 10 20:45:06 2020 +0100 source sha:aefb6aaf6475b71668bab7e11ce51b0fdc34f299 107486: tdf#41466 DOCX import: fix VML v:shape/v:textbox | https://gerrit.libreoffice.org/c/core/+/107486 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155550] text in docx missing
https://bugs.documentfoundation.org/show_bug.cgi?id=10 --- Comment #2 from raal --- Created attachment 187592 --> https://bugs.documentfoundation.org/attachment.cgi?id=187592=edit printscreen from Word -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155550] text in docx missing
https://bugs.documentfoundation.org/show_bug.cgi?id=10 raal changed: What|Removed |Added CC||r...@post.cz --- Comment #1 from raal --- Created attachment 187591 --> https://bugs.documentfoundation.org/attachment.cgi?id=187591=edit test file -- You are receiving this mail because: You are the assignee for the bug.
