[Libreoffice-bugs] [Bug 119567] Repeated print with deleted comments doesn't open printer window from 6.0
https://bugs.documentfoundation.org/show_bug.cgi?id=119567 --- Comment #8 from Kelly Kevin --- You have given a piece of detailed information, thank you so much for sharing this piece of writing here. I hope this is helpful for many of them who read your blog post. I have bookmarked this page for reading upcoming blog posts. I would be very thankful if you continue with the quality of what you are serving right now with your blog. I can say this is the perfect blog for everybody who read and post here every day. I don't know why I always visit here maybe it's so nice to read here interesting topics all day. So ill be back more to check more updates and new comments. I love blogging and love to read such informative blog posts. Keep on blogging with new content. I have shared this site with many of my friends. Essayacademia.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108626] LibreOffice Writer comment boxes are too small and should be resizable
https://bugs.documentfoundation.org/show_bug.cgi?id=108626 --- Comment #10 from Kelly Kevin --- You have given a piece of detailed information, thank you so much for sharing this piece of writing here. I hope this is helpful for many of them who read your blog post. I have bookmarked this page for reading upcoming blog posts. I would be very thankful if you continue with the quality of what you are serving right now with your blog. I can say this is the perfect blog for everybody who read and post here every day. I don't know why I always visit here maybe it's so nice to read here interesting topics all day. So ill be back more to check more updates and new comments. I love blogging and love to read such informative blog posts. Keep on blogging with new content. I have shared this site with many of my friends. Essayacademia.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108626] LibreOffice Writer comment boxes are too small and should be resizable
https://bugs.documentfoundation.org/show_bug.cgi?id=108626 --- Comment #9 from Kelly Kevin --- You have given a piece of detailed information, thank you so much for sharing this piece of writing here. I hope this is helpful for many of them who read your blog post. I have bookmarked this page for reading upcoming blog posts. I would be very thankful if you continue with the quality of what you are serving right now with your blog. I can say this is the perfect blog for everybody who read and post here every day. I don't know why I always visit here maybe it's so nice to read here interesting topics all day. So ill be back more to check more updates and new comments. I love blogging and love to read such informative blog posts. Keep on blogging with new content. I have shared this site with many of my friends. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145191] Hidden tables shouldn't set automatically write protected
https://bugs.documentfoundation.org/show_bug.cgi?id=145191 Robert Großkopf changed: What|Removed |Added Version|Inherited From OOo |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145191] Hidden tables shouldn't set automatically write protected
https://bugs.documentfoundation.org/show_bug.cgi?id=145191 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5186 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145186] Base Form can not access hidden filtered table when 'Content type' is a table and form is set "Analyze SQL" → 'yes'
https://bugs.documentfoundation.org/show_bug.cgi?id=145186 Robert Großkopf changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5191 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145191] New: Hidden tables shouldn't set automatically write protected
https://bugs.documentfoundation.org/show_bug.cgi?id=145191 Bug ID: 145191 Summary: Hidden tables shouldn't set automatically write protected Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Download https://bugs.documentfoundation.org/attachment.cgi?id=175795 Open the database. Start in pane "Queries" the query "Query_Starter". Content of the query will be shown. Query is write protected. SQL here: SELECT * FROM "starter" Close query. Go to Tolls → Table Filter… and set "starter" visible. Go to pane "Tables". Set View → Refresh Tables. Back to pane "Query" and start "Query_Starter". Query is now writable. There is no reason to set a hidden table only readable. Setting tables unvisible is only for getting a better overview. Every user of the database could set it back to show all tables. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145190] New: remote save cannot edit SSH service
https://bugs.documentfoundation.org/show_bug.cgi?id=145190 Bug ID: 145190 Summary: remote save cannot edit SSH service Product: LibreOffice Version: 5.2.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Created attachment 175802 --> https://bugs.documentfoundation.org/attachment.cgi?id=175802=edit Add-Edit SSH service.jpg: screenshots comparing add/edit - completely bogus. LibreOffice cannot edit the SSH remote save service. That has been true from day 1 (LO 5.1 when Remote Open/Save was introduced). At first, it only allowed changing the username (and OK remained greyed out). In LO 5.2, the full dialog showed up for editing, surprisingly based on bibisect-linux-64-5.2 commit 1991055d113a1ba9c56640eef867b25d3817607f author Jan Holesovsky on 2016-03-24 17:06:37 +0100 commit d2c1bc036de4b24a0f4602fbc7fd978fa8d603eb Disable gdrive/OneDrive/Alfresco cloud based on whether they are compiled in. The problem is that "ssh://" is not tied to any internet protocol, so it seems like the fix is to add urlobj INetProtocol::Ssh. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138071] "Save remote" fails with "This operation is not supported on this operating system"
https://bugs.documentfoundation.org/show_bug.cgi?id=138071 Justin L changed: What|Removed |Added CC||rob.fro...@wallawalla.edu --- Comment #5 from Justin L --- *** Bug 139132 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139132] Cannot save file to ssh:// mounted file system
https://bugs.documentfoundation.org/show_bug.cgi?id=139132 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Justin L --- *** This bug has been marked as a duplicate of bug 138071 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140748] Cannot save files on remote windows share server
https://bugs.documentfoundation.org/show_bug.cgi?id=140748 Justin L changed: What|Removed |Added Summary|CAnnot save files on remote |Cannot save files on remote |server |windows share server --- Comment #3 from Justin L --- Please provide much more details steps. Are you using "save remote"? (I assume you must be since your LO is running on Ubuntu.) What kind of file are you trying to save? Just an ODT? Are you getting an error message? Please provide the exact wording from it. If "open remote" can see the share, how can "save remote" not even see the share? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144897] I would like the available usable area for each slide o be increased to fit the maximum zoom (5%)
https://bugs.documentfoundation.org/show_bug.cgi?id=144897 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 144894] Numbering capter
https://bugs.documentfoundation.org/show_bug.cgi?id=144894 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 144893] Image frame & content split when dragging frame outside table & partly off page
https://bugs.documentfoundation.org/show_bug.cgi?id=144893 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 144874] Line spacing is temporally off (<1 second) when scroll down & back up (shift occurs)
https://bugs.documentfoundation.org/show_bug.cgi?id=144874 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 144862] Wiggling letter with window size of 1920 pixel width (72dpi) and zoom 140% (RSID?)
https://bugs.documentfoundation.org/show_bug.cgi?id=144862 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 143954] Menu rendering is broken (slow and jagged)
https://bugs.documentfoundation.org/show_bug.cgi?id=143954 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143954] Menu rendering is broken (slow and jagged)
https://bugs.documentfoundation.org/show_bug.cgi?id=143954 --- Comment #25 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141125] Can't Change Paper Size in Printer Properties - Newly introduced bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=141125 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 141125] Can't Change Paper Size in Printer Properties - Newly introduced bug.
https://bugs.documentfoundation.org/show_bug.cgi?id=141125 --- Comment #5 from QA Administrators --- Dear protonjunk454, 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 136085] The anchor to character/ to paragraph battle with an paragraph cross page
https://bugs.documentfoundation.org/show_bug.cgi?id=136085 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136085] The anchor to character/ to paragraph battle with an paragraph cross page
https://bugs.documentfoundation.org/show_bug.cgi?id=136085 --- Comment #4 from QA Administrators --- Dear Telesto, 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 136042] Freeze/layout loop after some delete action (LTR/RTL involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=136042 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 136018] The image in a image frame disappearing while moving the frame around with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=136018 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136042] Freeze/layout loop after some delete action (LTR/RTL involved)
https://bugs.documentfoundation.org/show_bug.cgi?id=136042 --- Comment #8 from QA Administrators --- Dear Telesto, 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 136018] The image in a image frame disappearing while moving the frame around with arrow keys
https://bugs.documentfoundation.org/show_bug.cgi?id=136018 --- Comment #4 from QA Administrators --- Dear Telesto, 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 135951] Image anchored to page vanished after changing it to character & pressing Undo (save & file reload bring it back)
https://bugs.documentfoundation.org/show_bug.cgi?id=135951 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 135951] Image anchored to page vanished after changing it to character & pressing Undo (save & file reload bring it back)
https://bugs.documentfoundation.org/show_bug.cgi?id=135951 --- Comment #5 from QA Administrators --- Dear Telesto, 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 141489] Inserting an image in a page with other images, sometimes other images disappear.
https://bugs.documentfoundation.org/show_bug.cgi?id=141489 --- Comment #2 from QA Administrators --- Dear David Horrocks, 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 136095] LibreOffice 7.0.0.3 (x64) Calc problems
https://bugs.documentfoundation.org/show_bug.cgi?id=136095 --- Comment #4 from QA Administrators --- Dear Robert, 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 96672] Outgoing mail server password in clear text inside the registrymodifications.xcu file
https://bugs.documentfoundation.org/show_bug.cgi?id=96672 --- Comment #8 from QA Administrators --- Dear michele, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96096] Brother QL570 Label-Printer, CTRL+P dialog -> print preview is damaged
https://bugs.documentfoundation.org/show_bug.cgi?id=96096 --- Comment #11 from QA Administrators --- Dear Thomas Mueller, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 79845] Mac OS X mdimporter for .odt files with tabulations doesn't import all text
https://bugs.documentfoundation.org/show_bug.cgi?id=79845 --- Comment #12 from QA Administrators --- Dear Dave Huang, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46959] PRINTING: Combination of Narrow Coloured Cell Border and Grid does not print correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=46959 --- Comment #12 from QA Administrators --- Dear Jeff Evans, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120496] Initial scrolling in Finder in a remote file directory is slow
https://bugs.documentfoundation.org/show_bug.cgi?id=120496 --- Comment #7 from QA Administrators --- Dear joe, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120190] Data "Formula to Value" don't preserve line break with multi-line text value
https://bugs.documentfoundation.org/show_bug.cgi?id=120190 --- Comment #7 from QA Administrators --- Dear antoine, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 111949] MAILMERGE: Wizards 3rd step page should change title according to the document type selected in 2nd step
https://bugs.documentfoundation.org/show_bug.cgi?id=111949 --- Comment #5 from QA Administrators --- Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145117] XML Source not imported if tags is non-ASCII symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=145117 --- Comment #11 from himajin100...@gmail.com --- >So this issue may be fixed after we upgrade orcus to the When I posted comment 4, I thought so, but I was wrong. LibreOffice master has a patch already merged on April https://gerrit.libreoffice.org/c/core/+/114892 , which is similar to the upstream so-called fix. https://gitlab.com/orcus/orcus/-/commit/2c2215e94bd8fce4b9a93e986339aa6ae06d2cba so I thought the bug was supposed to be fixed. I tested on latest master, and unfortunately the bug was still reproducible. I continued investigation on my own, and finally found the culprit as indicated on comment 9. -- sax_parser<_Handler,_Config>::element() https://gitlab.com/orcus/orcus/-/blob/master/include/orcus/sax_parser.hpp#L225 calls sax_parser<_Handler,_Config>::element_open(std::ptrdiff_t begin_pos) at https://gitlab.com/orcus/orcus/-/blob/master/include/orcus/sax_parser.hpp#L245 IF NO EXCEPTION IS THROWN, https://gitlab.com/orcus/orcus/-/blob/master/include/orcus/sax_parser.hpp#L255 and then calls parser_base::element_name(parser_element& elem, std::ptrdiff_t begin_pos) https://gitlab.com/orcus/orcus/-/blob/master/include/orcus/sax_parser.hpp#L255 https://gitlab.com/orcus/orcus/-/blob/master/src/parser/sax_parser_base.cpp#L394 ,which calls parser_base::name(std::string_view& str) https://gitlab.com/orcus/orcus/-/blob/master/src/parser/sax_parser_base.cpp#L333 -- the patch mainly focuses on parser_base::name(std::string_view& str), but the culprit is even before that. THE EXCEPTION WAS THORWN. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145117] XML Source not imported if tags is non-ASCII symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=145117 --- Comment #10 from Kevin Suo --- >orcus >* sax parser >* utf-8 names are now allowed as element names. So this issue may be fixed after we upgrade orcus to the ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145117] XML Source not imported if tags is non-ASCII symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=145117 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=96 ||499 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96499] FILEOPEN: HTML format .xls file shows NUMERIC cell value while TEXT type is expected (because ScHTMLQueryParser::ParseStyle has failed) (related to orcus)
https://bugs.documentfoundation.org/show_bug.cgi?id=96499 Kevin Suo changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5117 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145189] Crash doing a SaveAll of 21 documents
https://bugs.documentfoundation.org/show_bug.cgi?id=145189 --- Comment #2 from Jon R Kibler --- I just discovered that the crash left behind a temp file in the directory for these documents. It was empty, but before I deleted it, I captured some details in case they are of interest. Me:auditHome secaudit$ ls -hFal@eO lu96710be67vd.tmp -rw--- 1 secaudit secaudit -0B Oct 17 18:03 lu96710be67vd.tmp Me:auditHome secaudit$ $ stat -x lu96710be67vd.tmp File: "lu96710be67vd.tmp" Size: 0FileType: Regular File Mode: (0600/-rw---) Uid: ( 521/secaudit) Gid: ( 521/ secaudit) Device: 1,28 Inode: 7047Links: 1 Access: Sun Oct 17 18:03:21 2021 Modify: Sun Oct 17 18:03:21 2021 Change: Sun Oct 17 18:03:21 2021 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145157] Soft Edges effect distorting entire image in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145157 --- Comment #9 from Rafael Lima --- Created attachment 175801 --> https://bugs.documentfoundation.org/attachment.cgi?id=175801=edit Screenshot (left side has Soft Edges effect) Hi Regina! Thanks for your help with this issue. Indeed in your screenshot there's no visible distortion. So, I upload a screenshot of what I'm seeing. Note that the image in the right is more pixelated. This test was done in KDE using LO 7.3 alpha, but I had the same results in Windows. Can this be related to graphics card maybe? I use Nvidia in both my PCs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100030] LibreOffice Writer with AutoCorrection doesn't respect character style
https://bugs.documentfoundation.org/show_bug.cgi?id=100030 --- Comment #3 from Logan628 --- Give you a break. Handling all at once, like working, taking care of your health, studying and being socialized is close https://grademiners.com/ to impossible. We all need a break from time to time. A good essay writing service will provide you with such an opportunity. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145157] Soft Edges effect distorting entire image in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145157 --- Comment #8 from Regina Henschel --- Created attachment 175800 --> https://bugs.documentfoundation.org/attachment.cgi?id=175800=edit Screenshot: left part with soft edge, right part without I see no problem. With and without soft edge looks the same to me. The screenshots are from Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 93115d2c54d645bcf2f80fde325e3ede39dee4d5 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (en_US); UI: en-US Calc: CL -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94307] Child automatic character styles not recalculated correctly on reopening document
https://bugs.documentfoundation.org/show_bug.cgi?id=94307 --- Comment #12 from matthias.sonsti...@mailbox.org --- Version: 7.2.1.2 / LibreOffice Community Build ID: 2c9f9a7aa7c967a1b7ec3448959cff87b32f6580 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded Still present with the mentioned Linux LibreOffice Version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145189] Crash doing a SaveAll of 21 documents
https://bugs.documentfoundation.org/show_bug.cgi?id=145189 --- Comment #1 from Jon R Kibler --- I had 21 documents open to which I had been applying the same styles edit (Styles-->Load Styles from Template) on all documents. When I did a "SaveAll" LO successfully saved 13 of the documents but crashed leaving 8 to be recovered. The crash did not produce a crash dump (why?) but did produce the following errors in Console: error 18:01:12.822275 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:258563/0x3f203 rcv:0,send:0,d:1 limit:0). error 18:01:14.295500 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:124191/0x1e51f rcv:0,send:0,d:1 limit:0). error 18:01:15.255438 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:252759/0x3db57 rcv:0,send:0,d:1 limit:0). error 18:01:16.210905 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:239107/0x3a603 rcv:0,send:0,d:1 limit:0). error 18:01:17.679486 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:266759/0x41207 rcv:0,send:0,d:1 limit:0). error 18:01:18.670165 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:266027/0x40f2b rcv:0,send:0,d:1 limit:0). error 18:01:19.638232 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:302927/0x49f4f rcv:0,send:0,d:1 limit:0). error 18:01:20.680314 -0400 soffice 10759711: Error #17 (os/kern) invalid right attempting to add send right to port ( port:286983/0x46107 rcv:0,send:0,d:1 limit:0). All documents are in the same directory and all have the same ownership and permissions. LO has full disk access, too. LO did NOT restart after crash, nor did it give any indication it was going down the tubes -- it simply "vanished" from the desktop. When I manually restarted it, it indicated that it had 8 documents to recover. I cancelled the recovery, quit LO and restarted it. I was then able to successfully edit and save those 8 documents. System specifics: macOS 10.14.6 (18G9323) Mojave Version: 7.2.2.2 / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 8; OS: Mac OS X 10.14.6; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded This issue isn't cleanly reproducible, but I have had a bunch of errors with using Templates in 7.x and this seems to be just another one of them. See also: bugs 145167 and 145168. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125582] FILEOPEN PPTX follow path text transformation is different in LO and PowerPoint
https://bugs.documentfoundation.org/show_bug.cgi?id=125582 --- Comment #4 from Regina Henschel --- Szymon Klos has changed the vertical alignment for textArchUp and textArchDown to "Bottom" in https://git.libreoffice.org/core/+/a643c8353754c6ce8b318e37cbbc60c3425e9d32 I will add the same for textCircle, currently in https://gerrit.libreoffice.org/c/core/+/123726. That brings rendering nearer to PowerPoint. There are still problems: A LibreOffice considers for vertical alignment the actual bounding rectangle of the characters. PowerPoint considers the total line height including space for descenders, regardless of whether such occur or not. Also handling of line-spacing seems to be different. B PowerPoint places the letters without gap, same as in normal text. The letters have additional distances from each other in LibreOffice. ODF has the attribute draw:text-path-mode to distinct these ways from another, but that attribute is not implemented yet. The way PowerPoint writes the text would be the attribute value 'normal', LibreOffice's way the attribute value 'path'. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145189] New: Crash doing a SaveAll of 21 documents
https://bugs.documentfoundation.org/show_bug.cgi?id=145189 Bug ID: 145189 Summary: Crash doing a SaveAll of 21 documents Product: LibreOffice Version: 7.2.2.2 release Hardware: x86-64 (AMD64) OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jrk1231...@nym.hush.com -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145157] Soft Edges effect distorting entire image in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145157 Rafael Lima 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 144826] Conditional formatting works in Base table, not in forms
https://bugs.documentfoundation.org/show_bug.cgi?id=144826 --- Comment #16 from robinwalte...@gmail.com --- Robert Großkopf - that DOES work, thank you! Nice to know that it was as simple as setting the font colour to automatic. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145157] Soft Edges effect distorting entire image in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145157 --- Comment #7 from Rafael Lima --- In Slide 2 of the new sample files I wrote "Without Soft Edges Effects" but what I meant is "With Soft Edges Effects". So, the correct text is: Slide 1: Without Effects Slide 2: With Soft Edges Effects -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145157] Soft Edges effect distorting entire image in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145157 --- Comment #6 from Rafael Lima --- Created attachment 175799 --> https://bugs.documentfoundation.org/attachment.cgi?id=175799=edit PDF Sample File - Ex 2 Notice that the distortion also appears in the PDF file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145158] character format dialog doesn't show the current character size any more
https://bugs.documentfoundation.org/show_bug.cgi?id=145158 --- Comment #6 from himajin100...@gmail.com --- sorry for spamming, but now it became clear that this bugzilla system did not recognize '!' as a part of the URL. I often copy-paste a URL from some links in the URL and change its part. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145157] Soft Edges effect distorting entire image in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=145157 --- Comment #5 from Rafael Lima --- Created attachment 175798 --> https://bugs.documentfoundation.org/attachment.cgi?id=175798=edit ODP Sample File - Ex 2 I created another example that better illustrates the distortion I am seeing and uploaded it both as ODP and PDF. This time around I used a polygon-based image. In the first slide I added the original image without any effects. In the second slide I applied the Soft Edges effect. The distortion can be seen both in edit and presentation modes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145158] character format dialog doesn't show the current character size any more
https://bugs.documentfoundation.org/show_bug.cgi?id=145158 --- Comment #5 from himajin100...@gmail.com --- (or maybe I was missing '!' in the URL) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145158] character format dialog doesn't show the current character size any more
https://bugs.documentfoundation.org/show_bug.cgi?id=145158 --- Comment #4 from himajin100...@gmail.com --- actually, it was my fault. I didn't understand the ^ part in the URL (previous commit of the given id?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145158] character format dialog doesn't show the current character size any more
https://bugs.documentfoundation.org/show_bug.cgi?id=145158 --- Comment #3 from Mike Kaganski --- (In reply to Mike Kaganski from comment #2) Wait, it was (and still is) something with my browser: it opens 20305894243e24eb383ab9feefebf4a0e9f2644f when I click on the link in comment 1. Will look what could be the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145158] character format dialog doesn't show the current character size any more
https://bugs.documentfoundation.org/show_bug.cgi?id=145158 --- Comment #2 from Mike Kaganski --- (In reply to himajin10 from comment #1) The bisect is wrong - maybe something odd with bisect repo. Another bisect needed, e.g. on a different OS. The mentioned commit definitely has nothing to do with the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145080] make sure, cell selection colors use good contrast when following system highlight color on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=145080 Adolfo Jayme changed: What|Removed |Added URL||https://developer.apple.com ||/design/human-interface-gui ||delines/macos/visual-design ||/color/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145188] New: New line when typing á é í ó ú characters
https://bugs.documentfoundation.org/show_bug.cgi?id=145188 Bug ID: 145188 Summary: New line when typing á é í ó ú characters Product: LibreOffice Version: 7.2.1.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: a...@correia.pt I write in portuguese Whenever typing the characters á é í ó and ú a new line is created right after I type the ´character (cursor shoud wait for the letter, but it doesn't and creates a new line. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145158] character format dialog doesn't show the current character size any more
https://bugs.documentfoundation.org/show_bug.cgi?id=145158 himajin100...@gmail.com changed: What|Removed |Added CC||mikekagan...@hotmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from himajin100...@gmail.com --- $ git bisect log # bad: [3a2bb2f0e2e56def58d4ffea7ca5962c674829e3] source sha:8fdbb8aed1b48734a717d5f98ada566de7204605 # good: [0de175072f79362baeb83b6733b9300d4de5fba4] source sha:738bcf5e9a8c443d60c29c3a8068e8c16c72638a git bisect start 'latest' 'oldest' # bad: [7a711a39141eeaffb2bd55f93e928a8d2f4d42fb] source sha:3dfb8552eb84eaf831c4c3eb59c398afc87e9174 git bisect bad 7a711a39141eeaffb2bd55f93e928a8d2f4d42fb # good: [2de8b95e76962eb7baa9c1cb7b0e6c6f03dfb5b9] source sha:4b55847b81fa18d5bf2445c294b9260e98f365bc git bisect good 2de8b95e76962eb7baa9c1cb7b0e6c6f03dfb5b9 # bad: [f1d9f95447e3c586dea0869784dfa6bf6b983f08] source sha:c8976bdfdfa361fec9e1e5ff342094e409981fad git bisect bad f1d9f95447e3c586dea0869784dfa6bf6b983f08 # good: [b7adf1e1f69132b2ac805cab0e4d5050f29d6ca4] source sha:acfd369ebbd59d64290a846f49815592b6b95b30 git bisect good b7adf1e1f69132b2ac805cab0e4d5050f29d6ca4 # good: [5203c601d6f7c711fe49abac2bc702540061f795] source sha:5a4b588f3ab9412f6ae6763827020b0e90b568d6 git bisect good 5203c601d6f7c711fe49abac2bc702540061f795 # good: [1702d6cb2cecb3dd0badcafe77efd542b1776622] source sha:d1d56ed835549bb10995d4d240abf692e198bf78 git bisect good 1702d6cb2cecb3dd0badcafe77efd542b1776622 # bad: [d87974fdad85d7e3b19e5e8abaa189dbc8cf00d0] source sha:48d655fe12bc2c4c42d6c88b8a43fade1614ee2a git bisect bad d87974fdad85d7e3b19e5e8abaa189dbc8cf00d0 # bad: [b6fd136fec8600f017e69767fd4420117e7af2e9] source sha:1fa83df607b9721c8f12125942de1c586a624bd0 git bisect bad b6fd136fec8600f017e69767fd4420117e7af2e9 # bad: [6206672e9305ee8ad839fa1ca45e109f21efdc50] source sha:de355293303ace942c6f18df57400e0f26b9af29 git bisect bad 6206672e9305ee8ad839fa1ca45e109f21efdc50 # good: [7f912b7d10cd7427a1089662ec38de60e895ee41] source sha:e1948634a55ac91c7a49beda358b770b46b55b01 git bisect good 7f912b7d10cd7427a1089662ec38de60e895ee41 # good: [0188ce09b6dde06dacedca14145814f005cd81f5] source sha:863ee228e002cc9a0970a1d01f6028710bd997bc git bisect good 0188ce09b6dde06dacedca14145814f005cd81f5 # good: [3b41ddb0a9978caa3cabc30f51ae097e8b294672] source sha:20305894243e24eb383ab9feefebf4a0e9f2644f git bisect good 3b41ddb0a9978caa3cabc30f51ae097e8b294672 # bad: [f4fb2751ed6f66bf11f9e6c70471d53f14513f68] source sha:cfff893b9c82843a90aac4ecdb3a3936721b74a0 git bisect bad f4fb2751ed6f66bf11f9e6c70471d53f14513f68 # first bad commit: [f4fb2751ed6f66bf11f9e6c70471d53f14513f68] source sha:cfff893b9c82843a90aac4ecdb3a3936721b74a0 https://git.libreoffice.org/core/+/cfff893b9c82843a90a%5E! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46733] Deleting columns in a table can delete several columns if any cells in that column are merged with other cells
https://bugs.documentfoundation.org/show_bug.cgi?id=46733 --- Comment #29 from zhouss...@gmail.com --- Replicated the Report I installed Writer in my computer which is Windows 10.0.18363, x64-based PC. Follow the steps, I could reproduce the issue. Just step 3 and 4, I modify a bit with : 3) Select a cell of a different row in one of these columns 4) right click, and select "delete" --"columns" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145181] LibreOffice Math does not register ^
https://bugs.documentfoundation.org/show_bug.cgi?id=145181 --- Comment #4 from daniel-gen...@aon.at --- Adding letters after writing ^ used to work and it was not a problem for me, however it does not work since 7.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145181] LibreOffice Math does not register ^
https://bugs.documentfoundation.org/show_bug.cgi?id=145181 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #3 from m.a.riosv --- In some keyboard'a layout, it is a death key, adding a space after it should work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145185] Name box -> Manage Names -> Range Options -> 'Filter' is not persisted
https://bugs.documentfoundation.org/show_bug.cgi?id=145185 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Created attachment 175797 --> https://bugs.documentfoundation.org/attachment.cgi?id=175797=edit Sample file saved with 7.1.6 Works for me with Version: 7.2.2.2 (x64) / LibreOffice Community Build ID: 02b2acce88a210515b4a5bb2e46cbfb63fe97d56 CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL Version: 7.1.6.2 (x64) / LibreOffice Community Build ID: 0e133318fcee89abacd6a7d077e292f1145735c3 CPU threads: 4; OS: Windows 10.0 Build 21390; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144782] LibreOffice_7.2.1_Win_x64.msi (323 MB) not downloading
https://bugs.documentfoundation.org/show_bug.cgi?id=144782 Adolfo Jayme changed: What|Removed |Added Alias|WackyMe | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145183] FIND() function cannot detect a decimal point within a zero field
https://bugs.documentfoundation.org/show_bug.cgi?id=145183 --- Comment #6 from m.a.riosv --- (In reply to m.a.riosv from comment #5) > Don't mix the value inside the cell with the format of how it is showed. And > it can be point or command depending on the locale. > > If you want to get the integer part of the value, you can use > =INT(A1) > =ROUND(A1) > as text > =TEXT(A1;"0") point or comma -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145183] FIND() function cannot detect a decimal point within a zero field
https://bugs.documentfoundation.org/show_bug.cgi?id=145183 --- Comment #5 from m.a.riosv --- Don't mix the value inside the cell with the format of how it is showed. And it can be point or command depending on the locale. If you want to get the integer part of the value, you can use =INT(A1) =ROUND(A1) as text =TEXT(A1;"0") -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95336] FILESAVE Saving a Document with "#" in name (libreoffice dialogs)
https://bugs.documentfoundation.org/show_bug.cgi?id=95336 --- Comment #12 from Michael Warner --- Still an issue in: Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 6; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145183] FIND() function cannot detect a decimal point within a zero field
https://bugs.documentfoundation.org/show_bug.cgi?id=145183
--- Comment #4 from Michael Warner ---
In the example file I attached, column A is formatted to display 2 decimal
places. If you enter in 0 (or any other whole number for that matter) it shows
just the whole number in the formula bar (it shows just "0"), and the number
with two decimal places in the sheet ("0.00").
If you enter in a number with an actual fractional component, it shows that in
both places. For example, on row two I entered 0.01 and that displays both in
the formula bar and the sheet. There, the formula in column D works as
expected.
So, it seems clear that for any whole number, it's not considered to have a
decimal point, even though one is shown on the sheet. I can see why this would
surprise a person, but I don't know if it should really be considered a bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145183] FIND() function cannot detect a decimal point within a zero field
https://bugs.documentfoundation.org/show_bug.cgi?id=145183 --- Comment #3 from Michael Warner --- Created attachment 175796 --> https://bugs.documentfoundation.org/attachment.cgi?id=175796=edit Example file maybe -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145183] FIND() function cannot detect a decimal point within a zero field
https://bugs.documentfoundation.org/show_bug.cgi?id=145183 Michael Warner changed: What|Removed |Added Summary|[1] |FIND() function cannot ||detect a decimal point ||within a zero field -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145175] ConfigManager is not empty when quitting LO Writer (and LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=145175 Eyal Rozenberg changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Bug 140879 depends on bug 145175, which changed state. Bug 145175 Summary: ConfigManager is not empty when quitting LO Writer (and LO) https://bugs.documentfoundation.org/show_bug.cgi?id=145175 What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|NOTABUG |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145175] ConfigManager is not empty when quitting LO Writer (and LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=145175 Eyal Rozenberg changed: What|Removed |Added Ever confirmed|1 |0 Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED --- Comment #7 from Eyal Rozenberg --- (In reply to Noel Grandin from comment #5) > LibreOffice generates tons of false positive warnings, It actually generates very few false warnings. At least the daily master branch build, anyway. > it is just one of those things that happens, no need to worry. Either this is a false warning, in which case it should not be made; or it is a valid warning, in which case the config manager should be emptied. Which is it? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141773] Autocorrection for all languages doesn't work anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=141773 tommy27 changed: What|Removed |Added Summary|Autocorrection for all |Autocorrection for all |languages |languages doesn't work ||anymore --- Comment #12 from tommy27 --- I stumbled upon this bug today when I upgraded from 7.0.4.2 to 7.1.5.2 I can also tell the issue is still present in 7.2.0.0 too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145175] ConfigManager is not empty when quitting LO Writer (and LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=145175
--- Comment #6 from Julien Nabet ---
Noel: so does it mean we may remove the SAL_WARN_IF in:
152 utl::ConfigManager::~ConfigManager() {
153 SAL_WARN_IF(!items_.empty(), "unotools.config", "ConfigManager not
empty");
154 }
to reduce console noise?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145186] Base Form can not access hidden filtered table when 'Content type' is a table and form is set "Analyze SQL" → 'yes'
https://bugs.documentfoundation.org/show_bug.cgi?id=145186 --- Comment #4 from Robert Großkopf --- (In reply to intmail01 from comment #3) > For my usage the write protection is not good idea. The goal is not to > prevent table modification because this can be done on the server. You are right. Hiding tables in Base is only for good looking - couldn't be protected. But for this moment all queries will show a hidden table also write protected. So this bug is: Show also the table write protected in a form. An enhancement would be: Don't set a table write protected, if it is only set unvisible in Base. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140635] Options for auto correction need 22 seconds to open and a correction cannot be found / disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=140635 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||ilmari.lauhakangas@libreoff ||ice.org Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140879] [META] Console noise
https://bugs.documentfoundation.org/show_bug.cgi?id=140879 Bug 140879 depends on bug 145175, which changed state. Bug 145175 Summary: ConfigManager is not empty when quitting LO Writer (and LO) https://bugs.documentfoundation.org/show_bug.cgi?id=145175 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145175] ConfigManager is not empty when quitting LO Writer (and LO)
https://bugs.documentfoundation.org/show_bug.cgi?id=145175 Noel Grandin changed: What|Removed |Added Resolution|--- |NOTABUG Status|NEW |RESOLVED --- Comment #5 from Noel Grandin --- LibreOffice generates tons of false positive warnings, it is just one of those things that happens, no need to worry. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145186] Base Form can not access hidden filtered table when 'Content type' is a table and form is set "Analyze SQL" → 'yes'
https://bugs.documentfoundation.org/show_bug.cgi?id=145186 --- Comment #3 from intmail01 --- For my usage the write protection is not good idea. The goal is not to prevent table modification because this can be done on the server. The fact to hide a table is just for good looking and good design for the user working space on the screen, then display only essential tables. It help user to not have to navigate through too many table structure. Thanks for all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141773] Autocorrection for all languages
https://bugs.documentfoundation.org/show_bug.cgi?id=141773 Julien Nabet changed: What|Removed |Added CC||ba...@quipo.it --- Comment #11 from Julien Nabet --- *** Bug 145187 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145187] acor_und.dat autocorrect replacement table doesn't work anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=145187 Julien Nabet changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||serval2...@yahoo.fr --- Comment #1 from Julien Nabet --- It's a regression from a patch I did, see https://bugs.documentfoundation.org/show_bug.cgi?id=141773#c2 and following for more explanation. If you want to revert the patch, don't hesitate to. Autocorrect part is quite a mess. *** This bug has been marked as a duplicate of bug 141773 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77407] Option to Reduce Image Resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=77407 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5160 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145160] Writer Impress : the image compression form should select by default the former image format
https://bugs.documentfoundation.org/show_bug.cgi?id=145160 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=77 ||407 --- Comment #3 from Jérôme --- See bug 77407 comment 9. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145161] Writer Impress : the image compression form should change the image resolution only if it decreases
https://bugs.documentfoundation.org/show_bug.cgi?id=145161 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=77 ||407 --- Comment #3 from Jérôme --- See bug 77407 comment 9. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77407] Option to Reduce Image Resolution
https://bugs.documentfoundation.org/show_bug.cgi?id=77407 Jérôme changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||5161 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140854] Base VIEWING - table data redacted with black coloring for Memo [LONGVARCHAR] fields (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=140854 Aron Budea changed: What|Removed |Added Keywords||bisected -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145100] Applying numbered list style after bulleted increases its level
https://bugs.documentfoundation.org/show_bug.cgi?id=145100 niina-ma...@outlook.com changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from niina-ma...@outlook.com --- Hi, Thank you for reporting the bug. I have changed the status to NEEDINFO. Can you provide a test document and the actual results/expected results info so its easier to test your bug? When you have provided the test document and the extra info, you can change the status back to unconfirmed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145186] Base Form can not access hidden filtered table when 'Content type' is a table and form is set "Analyze SQL" → 'yes'
https://bugs.documentfoundation.org/show_bug.cgi?id=145186 Robert Großkopf changed: What|Removed |Added Summary|Base Form can not access|Base Form can not access |hidden filtered table when |hidden filtered table when |'Content type' is a table |'Content type' is a table ||and form is set "Analyze ||SQL" → 'yes' Assignee|rob...@familiegrosskopf.de |libreoffice-b...@lists.free ||desktop.org Version|7.0.6.2 release |6.4.7.2 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145186] Base Form can not access hidden filtered table when 'Content type' is a table
https://bugs.documentfoundation.org/show_bug.cgi?id=145186 Robert Großkopf changed: What|Removed |Added Ever confirmed|0 |1 CC||rob...@familiegrosskopf.de Assignee|libreoffice-b...@lists.free |rob...@familiegrosskopf.de |desktop.org | Status|UNCONFIRMED |NEW --- Comment #2 from Robert Großkopf --- Created attachment 175795 --> https://bugs.documentfoundation.org/attachment.cgi?id=175795=edit Open the different forms. Form connected to table with "Analyze SQL - Yes" don't find the table. Have tested it with different forms. Only the form, which is linked to a table and is set to "Analyze SQL → 'Yes'" shows an error. All other forms will show the content. But: All other forms will only show the content. The content is write protected. I would prefer to show a warning "content is write protected, because table is hidden" or something else. And then: Open the form in write protected mode. My system: OpenSUSE 15.2 64bit rpm Linux. Tested with different versions of LO, fails in LO 7.2.2.2, also in LO 6.4.7.2. Could be a bug introduced by OOo. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140854] Base VIEWING - table data redacted with black coloring for Memo [LONGVARCHAR] fields (macOS)
https://bugs.documentfoundation.org/show_bug.cgi?id=140854 --- Comment #32 from Yannick Chiron --- Bug still present in the released version LibreOffice 7.2.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145187] New: acor_und.dat autocorrect replacement table doesn't work anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=145187 Bug ID: 145187 Summary: acor_und.dat autocorrect replacement table doesn't work anymore Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Linguistic Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ba...@quipo.it CC: so...@libreoffice.org Description: that replacement list that worked as a global all-language autocorrect database, is not working anymore in LibO 7.1.5.2 (Windows) all the autocorrect entries inside that file are ignored by LibO while typing... the replacement list is still accessible from the Tools/Autocorrect menu (you gotta find [All] at the top of the list) but the text replacement is not applied. seems a regression from the 7.0.4.2 version I was using before upgrading Steps to Reproduce: . Actual Results: . Expected Results: . Reproducible: Always User Profile Reset: No Additional Info: . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145186] Base Form can not access hidden filtered table when 'Content type' is a table
https://bugs.documentfoundation.org/show_bug.cgi?id=145186 --- Comment #1 from intmail01 --- Created attachment 175794 --> https://bugs.documentfoundation.org/attachment.cgi?id=175794=edit Table missing error message -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145186] New: Base Form can not access hidden filtered table when 'Content type' is a table
https://bugs.documentfoundation.org/show_bug.cgi?id=145186 Bug ID: 145186 Summary: Base Form can not access hidden filtered table when 'Content type' is a table Product: LibreOffice Version: 7.0.6.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: intmai...@gmail.com Description: When I hide a table with the menu Tools > Table Filter then any query based on this table can always access it. But with Form it shows an error message when 'Content type' is a Table based on the hidden one. It is good thing to let Form to access an hidden table like in query. (When doing tests please save, close then re-open the .odb file) Steps to Reproduce: 1.Hide the table with menu Tools > Table Filter 2.Save the file, close, then reopen it 2.Open the form 3.An error message box is displayed Actual Results: Error message box Expected Results: No error Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.0.6.2 Build ID: 144abb84a525d8e30c9dbbefa69cbbf2d8d4ae3b CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Locale: fr-FR (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145117] XML Source not imported if tags is non-ASCII symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=145117 --- Comment #9 from himajin100...@gmail.com --- https://gitlab.com/orcus/orcus/-/blob/master/include/orcus/sax_parser.hpp#L244 https://gitlab.com/orcus/orcus/-/blob/master/include/orcus/sax_parser.hpp#L252 there may be more is_alpha() thingy in non-element-related code. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145117] XML Source not imported if tags is non-ASCII symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=145117 --- Comment #8 from himajin100...@gmail.com --- Created attachment 175793 --> https://bugs.documentfoundation.org/attachment.cgi?id=175793=edit NonReproducible XML file. Names start with ascii-alpha -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145117] XML Source not imported if tags is non-ASCII symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=145117 --- Comment #7 from himajin100...@gmail.com --- Created attachment 175792 --> https://bugs.documentfoundation.org/attachment.cgi?id=175792=edit Reproducible XML file. Names start with (non-(ascii-alpha)) -- You are receiving this mail because: You are the assignee for the bug.
