[Libreoffice-bugs] [Bug 144485] Regression: Cannot set line color in LibO 7.2 with KF5 VCL
https://bugs.documentfoundation.org/show_bug.cgi?id=144485 --- Comment #6 from Michael Weghorn --- (In reply to sergio.callegari from comment #4) > Incidentally, is there a tracking bug to collect as dependencies the items > where the KF5 VCL has issues wrt the GTK3 one? Is 102495 still relevant? > Should this issue land there? I have some other KF5 bugs open that should > probably go there if it is still used... Yes, bug 102495 is still used to track kf5-specific issues. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144554] Merged cell's image background is duplicated since 7.1
https://bugs.documentfoundation.org/show_bug.cgi?id=144554 --- Comment #3 from Alexander --- https://www.facebook.com/photo/?fbid=998998127311041=pcb.4936625299687497&__cft__[0]=AZXNz1q5Dl3R4fCRwk3920-p0YS_snJf9Z30EATyvo9-B1kAheTaPUQs_TXazPEquxmp9YnPBGSM1TTjTMDl2WfUCsECPojnIJu99qFae5O6CfJNW8t96xqUqdLyafTuuuRmuH5Z_oZFEyZxPouoOtJ9&__tn__=*bH-R https://www.facebook.com/photo/?fbid=999003193977201=pcb.4936625299687497&__cft__[0]=AZXNz1q5Dl3R4fCRwk3920-p0YS_snJf9Z30EATyvo9-B1kAheTaPUQs_TXazPEquxmp9YnPBGSM1TTjTMDl2WfUCsECPojnIJu99qFae5O6CfJNW8t96xqUqdLyafTuuuRmuH5Z_oZFEyZxPouoOtJ9&__tn__=*bH-R -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137173] Fileopen: DOC with hyperlinks hangs
https://bugs.documentfoundation.org/show_bug.cgi?id=137173 --- Comment #7 from Robert --- Still reproducible with 7.2.1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144309] Writer: Flow chart elements are not connected properly after save/load or zoom in/out
https://bugs.documentfoundation.org/show_bug.cgi?id=144309 Dieter changed: What|Removed |Added Ever confirmed|0 |1 CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO --- Comment #4 from Dieter --- Ilija, thank you for reporting the bug. Please attach the document from screenshots as odt-file, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136091] When in a writer document on secondary display, text get's garbled
https://bugs.documentfoundation.org/show_bug.cgi?id=136091 Dieter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #5 from Dieter --- (In reply to RFEMN from comment #3) > Just tested with version 7.0.5.2 and it appears to be fixed. => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134983] Positioning the image next to the text is rather hard. Text moves up or down
https://bugs.documentfoundation.org/show_bug.cgi?id=134983 Dieter changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #10 from Dieter --- (In reply to Telesto from comment #9) > [More interesting compared to my initial report :-)] That would be an interesting enhancement. So perhaps you should open an new report for this enhancement and close this bug here? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144317] minimize column width dont work on tables exceeding page limits in normal view
https://bugs.documentfoundation.org/show_bug.cgi?id=144317 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 144318] open by remote_files tries login with invalid users I do not specify
https://bugs.documentfoundation.org/show_bug.cgi?id=144318 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 144309] Writer: Flow chart elements are not connected properly after save/load or zoom in/out
https://bugs.documentfoundation.org/show_bug.cgi?id=144309 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 144308] Changing the DoAutoComplete attribute of the GlobalSheetSettings interface does not affect automatic completion of text in a cell is used.
https://bugs.documentfoundation.org/show_bug.cgi?id=144308 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 144260] 7.2.0: installation stops with error 1304
https://bugs.documentfoundation.org/show_bug.cgi?id=144260 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 140546] Takes a very long time to insert an image into a document
https://bugs.documentfoundation.org/show_bug.cgi?id=140546 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140546] Takes a very long time to insert an image into a document
https://bugs.documentfoundation.org/show_bug.cgi?id=140546 --- Comment #4 from QA Administrators --- Dear Heino Belz, 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 141177] pivot table has some odd numbers calculated
https://bugs.documentfoundation.org/show_bug.cgi?id=141177 --- Comment #5 from QA Administrators --- Dear vladvinhail, 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 141142] Fatal error since macOS Big Sur
https://bugs.documentfoundation.org/show_bug.cgi?id=141142 --- Comment #2 from QA Administrators --- Dear stephark, 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 140540] Crash in: mergedlo.dll trying to do mail merge print.
https://bugs.documentfoundation.org/show_bug.cgi?id=140540 --- Comment #2 from QA Administrators --- Dear kevin, 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 140425] El objeto aparecido NO PERMANECE
https://bugs.documentfoundation.org/show_bug.cgi?id=140425 --- Comment #2 from QA Administrators --- Dear Víctor Mencía Almansa, 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 140256] Cannot use mouse scroll button on selection buttons
https://bugs.documentfoundation.org/show_bug.cgi?id=140256 --- Comment #5 from QA Administrators --- Dear Quintao, 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 136192] Scrolling zooming decrease in performance in area's with a large table showing
https://bugs.documentfoundation.org/show_bug.cgi?id=136192 --- Comment #2 from QA Administrators --- Dear Telesto, 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 136188] Paste duplication after specific steps (track & changes probably involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=136188 --- Comment #3 from QA Administrators --- Dear Telesto, 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 136044] Columns seem off when deleting page break (hebrew)
https://bugs.documentfoundation.org/show_bug.cgi?id=136044 --- Comment #4 from QA Administrators --- Dear Telesto, 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 136019] Selecting a frame inside a frame or textbox inside a frame in header/footer is rather cumbersome
https://bugs.documentfoundation.org/show_bug.cgi?id=136019 --- Comment #4 from QA Administrators --- Dear Telesto, 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 135659] Images positioned wrongly after paste RFT undo regular paste
https://bugs.documentfoundation.org/show_bug.cgi?id=135659 --- Comment #4 from QA Administrators --- Dear Telesto, 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 135142] UNDO isn't removing styles inserted with RTF Special Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=135142 --- Comment #3 from QA Administrators --- Dear Telesto, 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 99562] Error rasterization of SVG gradients
https://bugs.documentfoundation.org/show_bug.cgi?id=99562 --- Comment #15 from QA Administrators --- Dear ape, 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] [Bug 97984] INSERT: SVG fill attribute is applied incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=97984 --- Comment #9 from QA Administrators --- Dear Xisco Faulí, 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] [Bug 97710] SVG import cant fill overlapped polyline
https://bugs.documentfoundation.org/show_bug.cgi?id=97710 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 97653] INSERT: woman's body not rendered in SVG
https://bugs.documentfoundation.org/show_bug.cgi?id=97653 --- Comment #8 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 97583] INSERT: SVG doesnt support blur
https://bugs.documentfoundation.org/show_bug.cgi?id=97583 --- Comment #10 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 91879] EDIT: wrong behaviour of a form's trigger when changing the record
https://bugs.documentfoundation.org/show_bug.cgi?id=91879 --- Comment #16 from QA Administrators --- Dear christian_kuhn, 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] [Bug 78232] Embedding PyGal SVG gives black box, but inkscape has no trouble
https://bugs.documentfoundation.org/show_bug.cgi?id=78232 --- Comment #6 from QA Administrators --- Dear tim-libreoffice, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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] [Bug 49773] FILEOPEN: failure to correctly read chart titles with sub-elements from Gnumeric ODS
https://bugs.documentfoundation.org/show_bug.cgi?id=49773 --- Comment #11 from QA Administrators --- Dear Andreas J Guelzow, 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] [Bug 41915] named cells not highlighted when editing formulae
https://bugs.documentfoundation.org/show_bug.cgi?id=41915 --- Comment #28 from QA Administrators --- Dear john, 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] [Bug 38443] Printer properties ignored from macros
https://bugs.documentfoundation.org/show_bug.cgi?id=38443 --- Comment #20 from QA Administrators --- Dear Oliver Brinzing, 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] [Bug 32743] Wrong layout when paste thousands calc cells in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=32743 --- Comment #13 from QA Administrators --- Dear Stefano Fraccaro, 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] [Bug 127670] LO --> insert .bmp file looks like black screen
https://bugs.documentfoundation.org/show_bug.cgi?id=127670 --- Comment #4 from QA Administrators --- Dear Vera Blagoveschenskaya, 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] [Bug 127659] "Apply" doesn't work in the options dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=127659 --- Comment #2 from QA Administrators --- Dear greatterrible, 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] [Bug 127575] Writer ODT with embedded scanned PDF image: image does not export to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=127575 --- Comment #17 from QA Administrators --- Dear xiphoid, 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] [Bug 124945] Minor UI glitch: color of selected item in drop down list
https://bugs.documentfoundation.org/show_bug.cgi?id=124945 --- Comment #4 from QA Administrators --- Dear Nicolas Christener, 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] [Bug 123916] Cannot switch between two document windows, if both property dialogs are opened
https://bugs.documentfoundation.org/show_bug.cgi?id=123916 --- Comment #2 from QA Administrators --- Dear Ulrich Windl, 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] [Bug 122022] PIVOTTABLE : Drill details filter whole row instead of one cell
https://bugs.documentfoundation.org/show_bug.cgi?id=122022 --- Comment #6 from QA Administrators --- Dear libreoffice-communaute, 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] [Bug 119975] UI: Zooming in print preview scrolls pages
https://bugs.documentfoundation.org/show_bug.cgi?id=119975 --- Comment #2 from QA Administrators --- Dear Manuel Vögele, 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] [Bug 116676] Function insertTextPortion() of XTextPortionAppend Interface doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=116676 --- Comment #8 from QA Administrators --- Dear Roland Baudin, 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] [Bug 102322] Incorrect Text Field appearance in exported PDF files
https://bugs.documentfoundation.org/show_bug.cgi?id=102322 --- Comment #7 from QA Administrators --- Dear alexrait, 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] [Bug 141415] DOC: FILEOPEN: Very slow document opening (2-5min instead of 20sec)
https://bugs.documentfoundation.org/show_bug.cgi?id=141415 --- Comment #6 from Igor D. --- Please, pay attension on this bug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144607] Bibliography database option does not open when selected
https://bugs.documentfoundation.org/show_bug.cgi?id=144607 Ismael Luceno changed: What|Removed |Added CC||ism...@iodev.co.uk --- Comment #3 from Ismael Luceno --- Even more problematic than the problem itself is that there is no error dialog, so the user can't tell what's wrong. I'm reporting on the same machine: $ dpkg -l libreoffice-\*|grep ^i ii libreoffice-base-core 1:7.1.5-0ubuntu0.21.04.1 amd64 office productivity suite -- shared library ii libreoffice-calc 1:7.1.5-0ubuntu0.21.04.1 amd64 office productivity suite -- spreadsheet ii libreoffice-common1:7.1.5-0ubuntu0.21.04.1 all office productivity suite -- arch-independent files ii libreoffice-core 1:7.1.5-0ubuntu0.21.04.1 amd64 office productivity suite -- arch-dependent files ii libreoffice-draw 1:7.1.5-0ubuntu0.21.04.1 amd64 office productivity suite -- drawing ii libreoffice-impress 1:7.1.5-0ubuntu0.21.04.1 amd64 office productivity suite -- presentation ii libreoffice-math 1:7.1.5-0ubuntu0.21.04.1 amd64 office productivity suite -- equation editor ii libreoffice-style-colibre 1:7.1.5-0ubuntu0.21.04.1 all office productivity suite -- colibre symbol style ii libreoffice-writer1:7.1.5-0ubuntu0.21.04.1 amd64 office productivity suite -- word processor I tried updating the system software, creating a new user, and from that user launching LibreOffice Writer. Same result. No feedback from the application whatsoever, not even to stderr/stdout. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144037] kf5: Unable to insert table from toolbar button
https://bugs.documentfoundation.org/show_bug.cgi?id=144037 --- Comment #13 from Rizal Muttaqin --- (In reply to Jan-Marek Glogowski from comment #9) > FWIW: the patch also applies to 7.2.1. I somehow missed to backport it. > There was https://gerrit.libreoffice.org/c/core/+/122116, but too late :-( So, any chance 7.2.1 will be patched? This bug affects many UI elements which make LibO barely usable in kf5. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144612] Calc input lag on 7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=144612 --- Comment #1 from Vincent --- mitigation: stick with 7.1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144612] Calc input lag on 7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=144612 Vincent changed: What|Removed |Added Keywords||perf CC||n...@laposte.net -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144612] New: Calc input lag on 7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=144612 Bug ID: 144612 Summary: Calc input lag on 7.2 Product: LibreOffice Version: 7.2.1.1 rc Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: n...@laposte.net Description: keyboard input in an empty cell is slow. I start calc with a empty spread sheet. After navigating with arrows or mouse clicking on a cell, entering a value is slow. Steps to Reproduce: 1. Start Calc with an empty spreadsheet 2. Navigating to a cell with keyboard arrows or by mouse clicking 3. Begin to type anything Actual Results: It lags for more than 10 seconds. Everything (LibreOffice menu+rendering of cells) become unresponsive. Expected Results: I'd like to input my stuff in less than 2 seconds. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: - On 7.1.7, strangely, I enter the first character, it lags for 2 to 3 seconds and I am able to input the rest. Afterwards, inputting other values is fast. - On 7.2.0 or 7.2.1, at the first attempt to enter something, it lags for more than 10 seconds. Everything become unresponsive. -I've tried to disable Skia, HW acceleration and OpenCL since I've a rather old GPU (+10 years). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 --- Comment #16 from Luboš Luňák --- (In reply to Julien Nabet from comment #5) > should we use "Disable hardware acceleration" to set "UseSkia" at False ? No. Skia/Raster has nothing to do with hardware acceleration. > Heiko/Xisco/Luboš: Should we create a new entry like 'Disable Skia' or I don't quite see the point, we generally do not provide options to disable things that are expected to work. It makes sense to disable HW acceleration, because that depends on HW drivers, which are outside of our control. But 'Disable Skia' would be like 'Disable Gtk' or 'Disable Fontconfig', we don't provide options to disable fontconfig just because there may be a bug in it. > Luboš: I read in vcl/skia/README that "raster" was "CPU-based drawing (here > primarily used for debugging)" That's misleading, Raster is also used as a fallback when Vulkan is not available. (In reply to Mike Kaganski from comment #15) > Note e.g. vroundps, which is specific for AVX, while our baseline for > WindowsX64 is SSE2. > > This shows that my idea about the need to disable Skia/Raster is wrong, and > simply the bug around building Skia should be fixed. Or maybe it is already > fixed in a recent 7.2 version? I'm not aware of any difference here between 7.1 and 7.2, they both build SkRect using normal Clang settings which should target SSE2. But SkRect::round() is inline in the class, so it's possible there's one copy emitted built with AVX and then we get unlucky when the linker selects that one copy when merging. Since SkOpts_avx.cpp indirectly pulls in SkRect.h, that's most likely what's happening. I'll ask on the Skia mailing list. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144525] Allow fill for line strokes and borders of shapes
https://bugs.documentfoundation.org/show_bug.cgi?id=144525 --- Comment #5 from Lucas J --- Regina, thank you for your dedicated work with the LibreOffice community. I made this additional feature request since my previous request is not as clear and developers would have to search through the comments to find out what the report covers. The previous report does not emphasize the already existing ability to apply this desired feature to the fill of shapes and does not emphasize the existing workaround. If possible, I would prefer the previous request to either be removed or replaced with this one. However, I believe your discretion would be best on what we should do. As a supporter of LibreOffice, I would love to help develop this feature myself. While I am new to the project, I would love to contribute despite the time it may take to develop such a feature. Is it possible that I can send the ODF specification request to the people at OASIS? Do you have information on how I could proceed with this? I would love to continue to see this technology improve and be more available to everyone. I thank you so much for your time, knowledge, and dedication. I am looking forward to your response, and please have a good day! God bless. :) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 --- Comment #15 from Mike Kaganski --- (In reply to r2 from comment #0) > This bug was filed from the crash reporting server and is > br-2520800e-6840-4482-8a82-b0944a0ad962. Hm, I should had checked the report first. The problem is not with GPU. Indeed, it's a CPU illegal instruction, caused by some wrong instruction set used for building Skia. FTR: the disassembly of SkRect::round in 7.1.6.2 on Windows x64 official build is: > 7FFC5673B9C0 vmovups xmm0,xmmword ptr [rcx] > 7FFC5673B9C4 vaddps xmm0,xmm0,xmmword ptr > [__xmm@3f003f003f003f00 (07FFC567F05D0h)] > 7FFC5673B9CC mov rax,rdx > 7FFC5673B9CF vroundpsxmm0,xmm0,9 > 7FFC5673B9D5 vminps xmm0,xmm0,xmmword ptr > [__xmm@4eff4eff4eff4eff (07FFC567EC910h)] > 7FFC5673B9DD vmaxps xmm0,xmm0,xmmword ptr > [__xmm@ceffceffceffceff (07FFC567EC920h)] > 7FFC5673B9E5 vcvttps2dq xmm0,xmm0 > 7FFC5673B9E9 vmovups xmmword ptr [rdx],xmm0 > 7FFC5673B9ED ret Note e.g. vroundps, which is specific for AVX, while our baseline for WindowsX64 is SSE2. This shows that my idea about the need to disable Skia/Raster is wrong, and simply the bug around building Skia should be fixed. Or maybe it is already fixed in a recent 7.2 version? At least this is how it looks in 7.2.1.2 x64 official build: > 7FFC56583110 pushrsi > 7FFC56583111 sub rsp,60h > 7FFC56583115 movaps xmmword ptr [rsp+50h],xmm9 > 7FFC5658311B movaps xmmword ptr [rsp+40h],xmm8 > 7FFC56583121 movaps xmmword ptr [rsp+30h],xmm7 > 7FFC56583126 movaps xmmword ptr [rsp+20h],xmm6 > 7FFC5658312B mov rsi,rdx > 7FFC5658312E movups xmm6,xmmword ptr [rcx] > 7FFC56583131 addps xmm6,xmmword ptr > [__xmm@3f003f003f003f00 (07FFC56B5F530h)] > 7FFC56583138 movaps xmm0,xmm6 > 7FFC5658313B shufps xmm0,xmm6,0E7h > 7FFC5658313F callfloorf (07FFC56B58F07h) > 7FFC56583144 movaps xmm8,xmm0 > 7FFC56583148 movaps xmm0,xmm6 > 7FFC5658314B unpckhpdxmm0,xmm6 > 7FFC5658314F callfloorf (07FFC56B58F07h) > 7FFC56583154 movaps xmm9,xmm0 > 7FFC56583158 unpcklpsxmm9,xmm8 > 7FFC5658315C movaps xmm0,xmm6 > 7FFC5658315F callfloorf (07FFC56B58F07h) > 7FFC56583164 movaps xmm7,xmm0 > 7FFC56583167 shufps xmm6,xmm6,0E5h > 7FFC5658316B movaps xmm0,xmm6 > 7FFC5658316E callfloorf (07FFC56B58F07h) > 7FFC56583173 unpcklpsxmm7,xmm0 > 7FFC56583176 movlhps xmm7,xmm9 > 7FFC5658317A minps xmm7,xmmword ptr > [__xmm@4eff4eff4eff4eff (07FFC56B5B850h)] > 7FFC56583181 maxps xmm7,xmmword ptr > [__xmm@ceffceffceffceff (07FFC56B5B860h)] > 7FFC56583188 cvttps2dq xmm0,xmm7 > 7FFC5658318C movups xmmword ptr [rsi],xmm0 > 7FFC5658318F mov rax,rsi > 7FFC56583192 movaps xmm6,xmmword ptr [rsp+20h] > 7FFC56583197 movaps xmm7,xmmword ptr [rsp+30h] > 7FFC5658319C movaps xmm8,xmmword ptr [rsp+40h] > 7FFC565831A2 movaps xmm9,xmmword ptr [rsp+50h] > 7FFC565831A8 add rsp,60h > 7FFC565831AC pop rsi > 7FFC565831AD ret -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144599] Page count before an endnote marker shows wrong number of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144599 --- Comment #5 from John --- (In reply to Peter Roelofsen from comment #3) No, I save it as ODT. I have just attached a test file. I hope with the test file it will be easier to understand what I mean. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144599] Page count before an endnote marker shows wrong number of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144599 --- Comment #4 from John --- Created attachment 175126 --> https://bugs.documentfoundation.org/attachment.cgi?id=175126=edit test file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144599] Page count before an endnote marker shows wrong number of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144599 --- Comment #3 from Peter Roelofsen --- (In reply to John from comment #2) > > I'm not sure if this would count as a bug. [...] > > The main problem is that even if you update a field by pressing F9 and save > your document, the field will revert to its un-updated state once you open > the document again. > > There is no such an issue with ToC. Once you updated it, you can safely > close the document and open it again. Updating ToC is boring at times, but > it works reliably and predictabely. > > In case of page count the issue is different and is much worse. After saving the field value is still correct. Do you save in docx format? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 --- Comment #14 from r2 --- not quite sure how, or WHO, to reply w/ this SIGNIFICANT discovery - but i think i've found at least a work-around, possibly a partial solution: i happen to have an identical Dell e6400 w/ w10 & LO & noticed it (msinfo.exe) has a diff. INF (oem49 v. oem46) file. then, i check the LO ver. & realized it's running 7.0.6.2, which i KNOW is/was working fine...uninstalled the 7.1.6 on the problem sys & installed w/ 7.0.6 - now appears to be working fine. interestingly, BOTH are denying that there's a update version & reporting "LibreOffice 7.0 is up to date." sorry i didn't think to cross-check my own available recourses but hope this will contribute to resolving whatever the ver. diff. issue / solution might be worth pursuing. Meny Gras! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132864] Harmony in position settings of different objects
https://bugs.documentfoundation.org/show_bug.cgi?id=132864 --- Comment #14 from Telesto --- (In reply to Telesto from comment #13) > This still needs some additional information: > If you drag the anchor (to character) doesn't move, except if you drag it to > different paragraph (where bullet counts as paragraph). > > Similar for position the image.. If you move the image into new paragraph, > the anchor will snap to new paragraph Note 1: the drag the anchor is slightly bugged: bug 144611 -- Note 2: To prevent misunderstanding: My primary concern is that the default settings for objects vary a lot across the board.. I see the current state more as historic process, based on incident & chaos. Like unfinished conversion (anchoring). Some look like mistakes: Paragraph *text* area/ paragraph area. The main request being that UX evaluates anchoring, alignment, wrapping defaults for the individual objects and integral 'anchor able objects as a whole'. Keeping in mind that user predictability decreases if you have plenty of objects with all their own defaults. It's impossible for me to tell the bigger picture/vision out how the individual objects behave. Or what the merits behind all those individual difference are. I think those variety of defaults having no purpose at all. Except - possibly - something (extension, unit test) somewhere relying on the current state of affairs. I'm convinced that there being bugs related to this, however it quite hard to tell right from wrong. - I do share Dieters view on documentation part (Help). Some kind of UX technical documentation at certain website (wiki) would be nice. Especially if the multitude of defaults are kept. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144498] Editing: Text copied from MS OneNote will not paste
https://bugs.documentfoundation.org/show_bug.cgi?id=144498 --- Comment #1 from patrick rall --- Descubre el mejor sitio donde comprar sillon descalzador en Internet. Mc Haus NAVIAN - Sillón para Salón, Butaca Comedor o Dormitorio, Escandinavo https://lamundial.net/sillones-descalzadores/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144502] Webdav: additional authorization in webdav storage when opening a document in kde
https://bugs.documentfoundation.org/show_bug.cgi?id=144502 --- Comment #1 from patrick rall --- Las cerraduras de embutir para puertas de madera son las más comunes que se instalan en viviendas, oficinas o locales comerciales. https://lamundial.net/cerraduras-madera-embutir/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144506] LO Base PUBLIC schema table data window shows no records
https://bugs.documentfoundation.org/show_bug.cgi?id=144506 --- Comment #5 from patrick rall --- Quieres comprar Cama nido 135x190? ¡Encuentralos aquí! ✓ Todo en stock y envío rápido. Si buscas comprar muebles online al mejor precio, esta es tu tienda. https://lamundial.net/camas-nido-135-x-190/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144515] Perf: slow operation on a Calc cell with huge text
https://bugs.documentfoundation.org/show_bug.cgi?id=144515 --- Comment #3 from patrick rall --- Butaca Vintage Garden, un clásico en nuestro catálogo. Un maravilla de sillón que le dará un toque cálido al espacio que ocupe https://lamundial.net/butacas-vintage/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144513] Perf: editengine hangs for *very* long time in TextEngine::CreateLines when trying to display a long line in a cell
https://bugs.documentfoundation.org/show_bug.cgi?id=144513 --- Comment #2 from patrick rall --- Encuentra Mesa Redonda Blanca - Muebles para el Hogar en MercadoLibre.com.mx! Entre y conozca nuestras increíbles ofertas y promociones. https://lamundial.net/mesas-de-centro-redondas-blancas/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144511] [DOCUMENTATION] Please describe how auto-save works in enough detail so users know when it will occur
https://bugs.documentfoundation.org/show_bug.cgi?id=144511 --- Comment #2 from patrick rall --- La mesa con tapa en MDF lacado blanco Ibiza es un mueble de última tendencia, que podrás utilizar tanto en la cocina como en el comedor https://lamundial.net/mesas-redondas-blancas/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144599] Page count before an endnote marker shows wrong number of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144599 --- Comment #2 from John --- > I'm not sure if this would count as a bug. [...] The main problem is that even if you update a field by pressing F9 and save your document, the field will revert to its un-updated state once you open the document again. There is no such an issue with ToC. Once you updated it, you can safely close the document and open it again. Updating ToC is boring at times, but it works reliably and predictabely. In case of page count the issue is different and is much worse. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 V Stuart Foote changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #13 from V Stuart Foote --- The crash report signature is filled with similar --> NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144611] Image position off when changing 'to paragraph' to 'to character' back 'to paragraph' and drag the anchor
https://bugs.documentfoundation.org/show_bug.cgi?id=144611 --- Comment #4 from Telesto --- Created attachment 175125 --> https://bugs.documentfoundation.org/attachment.cgi?id=175125=edit Example of opposite (changing from 'to paragraph' to 'to character') -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144607] Bibliography database option does not open when selected
https://bugs.documentfoundation.org/show_bug.cgi?id=144607 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- On pc Debian x86-64 with LO Debian testing package 7.1.5.2, I don't reproduce this. Did you install LO from Ubuntu repository? Could you give a try at https://wiki.documentfoundation.org/QA/FirstSteps#Corrupted_user_profile ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144611] Image position off when changing 'to paragraph' to 'to character' back 'to paragraph' and drag the anchor
https://bugs.documentfoundation.org/show_bug.cgi?id=144611 Telesto changed: What|Removed |Added Version|7.3.0.0 alpha0+ Master |4.4.0.3 release --- Comment #3 from Telesto --- Also in 4.4.7.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144611] Image position off when changing 'to paragraph' to 'to character' back 'to paragraph' and drag the anchor
https://bugs.documentfoundation.org/show_bug.cgi?id=144611 --- Comment #2 from Telesto --- STR to long: 1. open the attached file 2. Select the image 3. Change anchor to 'to paragraph' 4. Drag the anchor up to first paragraph -> Notice the mess 5. File -> reload 6. Change anchor to 'to paragraph' 7. Save 8. File -> reload 9. Drag the anchor up to first paragraph -> Expected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144611] Image position off when changing 'to paragraph' to 'to character' back 'to paragraph' and drag the anchor
https://bugs.documentfoundation.org/show_bug.cgi?id=144611 --- Comment #1 from Telesto --- Created attachment 175124 --> https://bugs.documentfoundation.org/attachment.cgi?id=175124=edit Example file -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144611] New: Image position off when changing 'to paragraph' to 'to character' back 'to paragraph' and drag the anchor
https://bugs.documentfoundation.org/show_bug.cgi?id=144611 Bug ID: 144611 Summary: Image position off when changing 'to paragraph' to 'to character' back 'to paragraph' and drag the anchor Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: Image position off when changing 'to paragraph' to 'to character' back 'to paragraph' and drag the anchor Steps to Reproduce: 1. open the attached file 2. Select the image 3. Change anchor to 'to paragraph' 4. Change it back to 'to character' 5. Change it again to 'to paragraph' 6. Drag the anchor up to first paragraph Actual Results: Image goes the left corner Expected Results: Should work similar to Step 3 Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: d5e55d204b71710eb5eb5d2c683dd6698626df3c CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144605] With View Grid Lines paper size limits appears but without View Grid Lines doesn't appear anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=144605 Julien Nabet changed: What|Removed |Added Summary|With View Grid Lines paper |With View Grid Lines paper |size limits appears but |size limits appears but |witout View Grid Lines |without View Grid Lines |doesn't appear anymore |doesn't appear anymore -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132864] Harmony in position settings of different objects
https://bugs.documentfoundation.org/show_bug.cgi?id=132864 --- Comment #13 from Telesto --- (In reply to Dieter from comment #12) > Additional suggestions: > "You can position an anchored item by dragging the item or the anchor itself > to > another location. This still needs some additional information: If you drag the anchor (to character) doesn't move, except if you drag it to different paragraph (where bullet counts as paragraph). Similar for position the image.. If you move the image into new paragraph, the anchor will snap to new paragraph -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 --- Comment #12 from Mike Kaganski --- (In reply to Julien Nabet from comment #7) My take: https://gerrit.libreoffice.org/c/core/+/122275 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137125] DF Formatting moving around in unexpected way with copy/paste
https://bugs.documentfoundation.org/show_bug.cgi?id=137125 --- Comment #15 from Telesto --- (In reply to Dieter from comment #14) > Discussion is important but clearly behind the scope of a bug report. So I > suggest to close it. I think it's reasonable to do? * Not sure if there is room for a sleeping bug related to comment 10 point 3? * Another options is to stag all similar bugs into a meta bug [even as closed bugs]. Simply to make it easier to find those back -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 --- Comment #11 from V Stuart Foote --- (In reply to r2 from comment #9) > Created attachment 175123 [details] > w/ redacted service tag > > per V Stuart Foote request/comment #8 OK thanks. Well to be expected the nVidia Quadro NVS 160M is suspect showing Direct 3D support only through 10.0 spec and OpenGL only to the 2.1 spec. Obviously no Vulkan support, but not surprised modern Skia drivers choke on the hardware. Assuming it exposes its identity to hw poling, the hardware/driver pair needs deny listing from any Skia rendering with immediate fallback to GDI only rendering. @Lubos, is that feasible? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83090] UI: Entered font sizes (e.g., 12.4 pt, 12.7 pt) are being rounded off (rather than up) in the toolbar / sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=83090 Andreas Heinisch changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |andreas.heini...@yahoo.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144608] Impress: Interference between text anchor and paragraph alignment
https://bugs.documentfoundation.org/show_bug.cgi?id=144608 --- Comment #1 from sergio.calleg...@gmail.com --- According to https://ask.libreoffice.org/t/lo-draw-why-do-i-have-to-use-text-anchors-instead-of-paragraph/27290 this has been going on since at least LibO 5.3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144610] New: Font drop down does not function correctly throughout the suite
https://bugs.documentfoundation.org/show_bug.cgi?id=144610 Bug ID: 144610 Summary: Font drop down does not function correctly throughout the suite Product: LibreOffice Version: 7.2.1.1 rc Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bria...@infinitesadness.net Description: Anywhere throughout LibreOffice where there is a font selection dropdown, choosing a different font has no effect whatsoever. In certain parts of the UI, the system does not even acknowledge you have chosen a different font; in a document, the font remains the default (or original formatting). This happens in all components of LibreOffice, as well as attempting to change the default font in the Options dialog for any component. Note: The font selection *list* in the Format > Character... and Edit Style dialog boxes function as expected, as does changing fonts through previously-defined styles. Steps to Reproduce: 1. Select any amount of text in a document (or spreadsheet, presentation etc.) 2. Select a new font from the Font dropdown control on the toolbar (or tab bar) OR while a component (Writer, Calc, Impress etc.) is open 1. Choose Tools > Options... 2. Expand "LibreOffice Writer" (or Calc, Impress etc.) 3. Choose Basic Fonts (Western) 4. Attempt to select a different font from any of the dropdown lists. Actual Results: The font does not change at all. * In a document, the font remains what it was. The dropdown control retains the name of the font you selected until it loses focus. * In the Options dialog, the software acts as if you clicked out of the dropdown list (or pressed Escape) Expected Results: The software should have changed the font of the selected text/cell, as well as changing the font name displayed in the dropdown control. In the Options dialog, the software should retain the font you selected, as well as changing the font in the user's profile/preferences data. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144163] LibreOffice 7.2 Firebird Embedded Base Error - field defined with 20 CHAR limit and containing more than 20 characters stored opens with 7.1, fails to open with 7.2
https://bugs.documentfoundation.org/show_bug.cgi?id=144163 --- Comment #9 from putman...@gmail.com --- (In reply to Alex Thurgood from comment #6) > Surely, it is a bug if you have a field with a defined character limit of 20 > and the software application nonetheless allows you to store more than 20 > characters, and then subsequently screws up restituting that character > string (or value) ? > > I would argue that this is buggy behaviour. > > Rings a bell though, as an already existing bug... Surely, it is a bug that is still there in release 7.2.1.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 --- Comment #10 from r2 --- (In reply to Julien Nabet from comment #1) > Could you give a try at > https://wiki.documentfoundation.org/QA/FirstSteps#Graphics-related_issues_. > 28Skia.29 ? it appears my reply-w/attached file/s email was rejected, i think THISS is the meat of the answer: Version: 7.1.6.2 (x64) / LibreOffice Community Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3 CPU threads: 2; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 34694] [META] Improve usability of error messages
https://bugs.documentfoundation.org/show_bug.cgi?id=34694 Bug 34694 depends on bug 123144, which changed state. Bug 123144 Summary: Unfriendly Error Message in VBASupport 1 https://bugs.documentfoundation.org/show_bug.cgi?id=123144 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144598] Crash in: SkRect::round()
https://bugs.documentfoundation.org/show_bug.cgi?id=144598 --- Comment #9 from r2 --- Created attachment 175123 --> https://bugs.documentfoundation.org/attachment.cgi?id=175123=edit w/ redacted service tag per V Stuart Foote request/comment #8 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144609] Numbering is unseen with prefix text
https://bugs.documentfoundation.org/show_bug.cgi?id=144609 Pierre C changed: What|Removed |Added CC||pierre.choffar...@free.fr Version|unspecified |7.2.1.1 rc OS|All |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144609] New: Numbering is unseen with prefix text
https://bugs.documentfoundation.org/show_bug.cgi?id=144609 Bug ID: 144609 Summary: Numbering is unseen with prefix text Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pierre.choffar...@free.fr Created attachment 175122 --> https://bugs.documentfoundation.org/attachment.cgi?id=175122=edit test document Step to reproduce Open attached file and compare the the text with the first screen copy First part of the file is the text with the problem then two screen copies First image the correct behaviour. So the text upper should be the same Second image is the bug, you can see the differences This bug seems to be same as : https://bugs.documentfoundation.org/show_bug.cgi?id=143784 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144554] Merged cell's image background is duplicated since 7.1
https://bugs.documentfoundation.org/show_bug.cgi?id=144554 psidiumcode changed: What|Removed |Added Keywords|bibisectRequest, regression |bisected Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from psidiumcode --- Git bisect log # bad: [116e9431a240e3a7c7161b9d7112c4a93c0363b3] source sha:d5e786d78d2f72a39f02746d6e0faa04da72c60a # good: [75306c92d72b1fb500c114873493cf9d3c824e76] source sha:574c57090642347980d2395e1e183cc7b5c171ad git bisect start 'master' 'oldest' # bad: [062dcd9049c6a969aee24685350fac959be03ee9] source sha:a0f282f57213c4318c1de10d74ee43b850886147 git bisect bad 062dcd9049c6a969aee24685350fac959be03ee9 # good: [51742fbd21633235caf30f80dc5b71274ee772ff] source sha:58b4ea44865cb7a058c35edaef62576e1bbebfc7 git bisect good 51742fbd21633235caf30f80dc5b71274ee772ff # bad: [3543654c94ec5c5c80a7c82cd51167866be6ee36] source sha:fc7464a882f22e7974135e44867d1a183881edd9 git bisect bad 3543654c94ec5c5c80a7c82cd51167866be6ee36 # good: [03bef7423657ec3016bf5c87ba4f2ae566803816] source sha:7eff43375d8d1df59d4961b9e8bc5d12b3edbab6 git bisect good 03bef7423657ec3016bf5c87ba4f2ae566803816 # bad: [86c5b8550bf9b85b56580f04ef2d629d8a29dc26] source sha:b6a4ddf4d8c45030dbe3fc68b51f9366109041bd git bisect bad 86c5b8550bf9b85b56580f04ef2d629d8a29dc26 # bad: [c370c148e9b4506694d36cef608a89deccca7820] source sha:06fd06597796d9e92117602245f3968c93707708 git bisect bad c370c148e9b4506694d36cef608a89deccca7820 # bad: [44c64c53911bcd77bcc782ae02e7714476b1a044] source sha:af2b82b4f32909dd82006e531398c68268325d24 git bisect bad 44c64c53911bcd77bcc782ae02e7714476b1a044 # good: [87b4315cda24c5cc87b9db04ffe783252a2ce77e] source sha:b827eefd6397dc34b49a03e186146aed6cd80042 git bisect good 87b4315cda24c5cc87b9db04ffe783252a2ce77e # bad: [1935f0e07648962bcce171c472cfd92d790add10] source sha:8197c3af338a20a3b99de001adc02b4329f074a7 git bisect bad 1935f0e07648962bcce171c472cfd92d790add10 # bad: [aec2b6a20958e45adb75c5798bbace1909d89116] source sha:7b4802070ac6fb930255536bf3ed2c52428b4181 git bisect bad aec2b6a20958e45adb75c5798bbace1909d89116 # bad: [90e448fddbc334b6f2d1a0ca8fe963417bcae4fb] source sha:7468d5df5ec79783eae84b62bdc5ecf12f0ca255 git bisect bad 90e448fddbc334b6f2d1a0ca8fe963417bcae4fb # bad: [2b1674cb292c04eb28bdab33c56e34e3a52a9e26] source sha:6e86f77da5cf66c832f785a7f4eb806a3fdc26c6 git bisect bad 2b1674cb292c04eb28bdab33c56e34e3a52a9e26 # bad: [c1f553a71172c0bf2d24e33219fcef7b56e1c383] source sha:c016fe2b5918d6e53113e100b1126076b6e1a6a3 git bisect bad c1f553a71172c0bf2d24e33219fcef7b56e1c383 # first bad commit: [c1f553a71172c0bf2d24e33219fcef7b56e1c383] source sha:c016fe2b5918d6e53113e100b1126076b6e1a6a3 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144554] Merged cell's image background is duplicated since 7.1
https://bugs.documentfoundation.org/show_bug.cgi?id=144554 --- Comment #1 from psidiumcode --- I could not reproduce it in ver: Version: 7.0.6.2 Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded I could reproduce it in ver: Version: 7.1.0.0.alpha0+ Build ID: CPU threads: 12; OS: Mac OS X 10.15.7; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Bisected with Mac bisect repo 7.1 (bibisect-mac64-7.1 https://bibisect.libreoffice.org/mac64-7.1.git) c1f553a71172c0bf2d24e33219fcef7b56e1c383 is the first bad commit commit c1f553a71172c0bf2d24e33219fcef7b56e1c383 Author: libreoffice Date: Sun Aug 2 12:49:36 2020 +0200 source sha:c016fe2b5918d6e53113e100b1126076b6e1a6a3 source sha:c016fe2b5918d6e53113e100b1126076b6e1a6a3 LibreOffice.app/Contents/Frameworks/libswlo.dylib | Bin 18469980 -> 18469980 bytes .../Contents/Resources/config/images_breeze.zip| Bin 1861811 -> 1861811 bytes .../Resources/config/images_breeze_dark.zip| Bin 1857484 -> 1857484 bytes .../Resources/config/images_breeze_dark_svg.zip| Bin 1531920 -> 1531920 bytes .../Resources/config/images_breeze_svg.zip | Bin 1529480 -> 1529480 bytes .../Contents/Resources/config/images_colibre.zip | Bin 2730776 -> 2730776 bytes .../Resources/config/images_colibre_svg.zip| Bin 2805657 -> 2805657 bytes .../Resources/config/images_elementary.zip | Bin 4011601 -> 4011601 bytes .../Resources/config/images_elementary_svg.zip | Bin 4989543 -> 4989543 bytes .../Resources/config/images_karasa_jaga.zip| Bin 4820615 -> 4820615 bytes .../Resources/config/images_karasa_jaga_svg.zip| Bin 19051896 -> 19051896 bytes .../Contents/Resources/config/images_sifr.zip | Bin 2075564 -> 2075564 bytes .../Contents/Resources/config/images_sifr_dark.zip | Bin 2077418 -> 2077418 bytes .../Resources/config/images_sifr_dark_svg.zip | Bin 1726964 -> 1726964 bytes .../Contents/Resources/config/images_sifr_svg.zip | Bin 1723171 -> 1723171 bytes .../Contents/Resources/config/images_sukapura.zip | Bin 3002843 -> 3002843 bytes .../Resources/config/images_sukapura_svg.zip | Bin 4292030 -> 4292030 bytes LibreOffice.app/Contents/Resources/setuprc | 2 +- LibreOffice.app/Contents/Resources/versionrc | 2 +- 19 files changed, 2 insertions(+), 2 deletions(-) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144599] Page count before an endnote marker shows wrong number of pages
https://bugs.documentfoundation.org/show_bug.cgi?id=144599 Peter Roelofsen changed: What|Removed |Added CC||floris...@gmail.com --- Comment #1 from Peter Roelofsen --- Confirmed on LibO 7.2.0.4 https://gerrit.libreoffice.org/gitweb?p=core.git;a=log;h=ce769e3009755dcf0082844e386f5dca4c8ecb2f in Ubuntu Linux 20. The page count field updates automatically when you add pages in the "normal" area, but not when you add an endnotes section. You have to do Tools - Update - Fields (or F9) to force the page count to update in some other way. Once updated, it will automatically update when you add so many endnotes that the text wraps to a second endnotes page. I'm not sure if this would count as a bug. I don't know how much auto-updating for such cases would cost in terms of time spent checking if the page count needs to be updated. Not auto-updating the ToC makes sense to me - it'd probably mean that Writer would have to check at virtually every new paragraph whether it's a paragraph that has to be added to the ToC. But it's definitely something that may give some users a headache. Do we want that? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142468] LibreOffice randomly hangs on macOS Big Sur 2020 MacBook Air M1
https://bugs.documentfoundation.org/show_bug.cgi?id=142468 --- Comment #12 from David W. Snow --- There was a question about what fonts I am using. The files use: Noto Serif, Noto Sans, Noto Mono, and may have a small section of Handlee. This is a handwriting script from Google. The Noto fonts ship with Libre Office. I use the Noto fonts because they display well on BOTH printed output and on screens. I was not editing text in the Handlee font at the time of any crash/hang. On some crashes/hangs I see the recovery dialog and on others, I do not. No idea why. --- Comment #13 from David W. Snow --- There was a question about what fonts I am using. The files use: Noto Serif, Noto Sans, Noto Mono, and may have a small section of Handlee. This is a handwriting script from Google. The Noto fonts ship with Libre Office. I use the Noto fonts because they display well on BOTH printed output and on screens. I was not editing text in the Handlee font at the time of any crash/hang. On some crashes/hangs I see the recovery dialog and on others, I do not. No idea why. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142468] LibreOffice randomly hangs on macOS Big Sur 2020 MacBook Air M1
https://bugs.documentfoundation.org/show_bug.cgi?id=142468 --- Comment #12 from David W. Snow --- There was a question about what fonts I am using. The files use: Noto Serif, Noto Sans, Noto Mono, and may have a small section of Handlee. This is a handwriting script from Google. The Noto fonts ship with Libre Office. I use the Noto fonts because they display well on BOTH printed output and on screens. I was not editing text in the Handlee font at the time of any crash/hang. On some crashes/hangs I see the recovery dialog and on others, I do not. No idea why. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137125] DF Formatting moving around in unexpected way with copy/paste
https://bugs.documentfoundation.org/show_bug.cgi?id=137125 --- Comment #14 from Dieter --- Discussion is important but clearly behind the scope of a bug report. So I suggest to close it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144603] spam
https://bugs.documentfoundation.org/show_bug.cgi?id=144603 Michael Warner changed: What|Removed |Added Status|RESOLVED|CLOSED Summary|Best Eyeglasses in |spam |Stafford, Texas | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132864] Harmony in position settings of different objects
https://bugs.documentfoundation.org/show_bug.cgi?id=132864 --- Comment #12 from Dieter --- (In reply to Telesto from comment #11) > A) Topic Default anchoring > Historically everything got anchored 'to paragraph'. Currently images / > charts are inserted by default 'to character' > https://cgit.freedesktop.org/libreoffice/core/commit/ > ?id=a7528cd6f17ea5c5b29e7d607e54c62de0d9e7db > > However other objects still have the 'to paragraph' anchoring (Frame, > Fontwork, Shape). Whereas the reason for changing it for images also valid > for the other objects, IMHO. I get the impression those where overlooked. > Images are obviously the most common. Or the assumption this would handle > all cases? Or simply didn't look into it, because the main concern being > images (but breaking coherence in the process) Suggestion: Add informations about default anchor in [1], for example: "To Character: ... This is the default anchor for images, ... and ..." > B) Topic Alignment I don't have enough insights to that topic. But perhaps information about alignment could be part of [2] > C) Topic Wrap > Different objects have different wrap settings. Like: Optimal > (images,charts), but bugged, some bug proposing change of default; Through > (textbox;fontwork, shapes). Frame (Parallel) I couldn't find an overview about different options for wrapping. this might include informtations about default wrap for different objects. Additional suggestions: Help [2] says: "You can position an anchored item by dragging the item to another location." More precise would be: "You can position an anchored item by dragging the item or the anchor itself to another location. It's also possible to use arrow keys." [1] https://help.libreoffice.org/latest/en-US/text/shared/01/0526.html [2] https://help.libreoffice.org/latest/en-US/text/swriter/guide/anchor_object.html?DbPAR=WRITER#bm_id3147828 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144594] hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144594 --- Comment #4 from Buovjaga --- (In reply to steve from comment #3) > this was a random writer test file with onle a few words in it and I no > longer have it :/ > Anything suspicious in the crash log? I don't know, but how would you verify that the bug is gone? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144585] button popups don't open with KF5 VCL on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=144585 --- Comment #3 from Buovjaga --- (In reply to Antonio Rojas from comment #2) > In kwin it doesn't open at all, no matter how many times I click. It does for me, just not for you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144603] Best Eyeglasses in Stafford, Texas
https://bugs.documentfoundation.org/show_bug.cgi?id=144603 Buovjaga changed: What|Removed |Added Component|BASIC |deletionRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144295] Shaded box covers menu and icons
https://bugs.documentfoundation.org/show_bug.cgi?id=144295 --- Comment #3 from welda...@gmail.com --- In safe mode the problem disappears until I apply a theme. (options > LibreOffice > Personalization > Preinstalled Theme ) Conversely, back in my original user profile, the problem goes away if I remove any theme. I also want to emphasize that this problem only starts to appear when the application is > ~75% screen width, and fully there at full screen width. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144594] hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144594 steve changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144594] hangs right after opening file
https://bugs.documentfoundation.org/show_bug.cgi?id=144594 --- Comment #3 from steve --- this was a random writer test file with onle a few words in it and I no longer have it :/ Anything suspicious in the crash log? -- You are receiving this mail because: You are the assignee for the bug.
