[Libreoffice-bugs] [Bug 45589] Show bookmarks: make them visible in a document
https://bugs.documentfoundation.org/show_bug.cgi?id=45589 --- Comment #18 from zionoto --- (In reply to Yousuf Philips (jay) (retired) from comment #6) > Google Docs is the only word processor that shows bookmarks MS word has the possibility to show bookmarks as non printable chars: the bookmarks are represented by square brackets as follows: [bookmarked text] please see the attached screenshot I have just tested. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45589] Show bookmarks: make them visible in a document
https://bugs.documentfoundation.org/show_bug.cgi?id=45589 --- Comment #17 from zionoto --- Created attachment 155159 --> https://bugs.documentfoundation.org/attachment.cgi?id=155159=edit ms Word book mark representation -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107738] [META] Section bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107738 Dieter Praas changed: What|Removed |Added Depends on||125455 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125455 [Bug 125455] Content in sections disappear and formatting gets distorted after reopening the file -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125455] Content in sections disappear and formatting gets distorted after reopening the file
https://bugs.documentfoundation.org/show_bug.cgi?id=125455 Dieter Praas changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Blocks||107738 --- Comment #4 from Dieter Praas --- Iqtedar, thank you for your document. That makes the problem more clear. But - as you also mentioned - it's not possible to reproduce the bug. So please try to provide a document, where is is possible - at least for you. Yu also can try, if an actual version of LO solves your problem. => Back to NEEDINFO Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107738 [Bug 107738] [META] Section bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 112695] impress not listening on bluetooth or tcp 1599 for remote connection
https://bugs.documentfoundation.org/show_bug.cgi?id=112695 --- Comment #7 from hgkamath --- android-6 -> win10/portableapps-libreoffice. * The bluetooth connection worked. However, the libreoffice process is unstable via bluetooth and will crash after a few swipes, especially when slides are interacted with on computer while being controlled on phone. The app on android was stable, no preview, shows blank slides with notes, was able to control until the crashing. Crashing of portable-libreoffice (win) under bluetooth would perhaps be a different bug on its own * direct-wifi from phone to win10 mobile-hotspot worked. Connection seemed stabler than bluetooth. App showed blank slides with notes, can swipe back and forth. win10 firewall prompts to open port on public and private networks, which is to be allowed. In either case, android app is stable, able to configure both bluetooth and wifi connections. Able to swipe back forth, but no preview of slides. perhaps feature is under development, else that would be a different bug. * unable to test the phone->VPN-wifi->win10 with my present setup/network, but it seems likely it will work. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128227] NAVIGATOR: Rename "Text Frame" to "Frame"
https://bugs.documentfoundation.org/show_bug.cgi?id=128227 --- Comment #7 from Dieter Praas --- (In reply to V Stuart Foote from comment #5) > Every object on document canvas will have a frame, a 'Text frame' is > specifically for managing text layout and can contain other objects. Images, > shapes, OLE objects, tables inserted into a 'Text frame' will still be > listed separately in Navigator. The 'Text frame' is the container, but its > function is to control flow of textual content in the layout--objects other > than text will flow in text along with their anchors. Linking 'Text frames' > is the way we layout the text on a page. Thnks for clarification, but a normal user (just me) doesn't know that. I could see, that Insert => Frame => Frame Interactively / Frame inserts an entry into the navigator, while Insert => Frame => Floating Frame doesn't. So my idea won't be the best solution, but I still think, that the actual situation is al little confusing. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120117] Sidebar Disrupts Column/Row Freeze Status
https://bugs.documentfoundation.org/show_bug.cgi?id=120117 --- Comment #5 from Kevin Suo --- (In reply to QA Administrators from comment #4) The bug still exists in the most recent version. Actually it's not only the side bar, but a window resize can also cause the column wor freeze to be corrupted. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 36709] First Line Indent Using Ch (Characters) as Units Won't Change Size as Font Size Grow
https://bugs.documentfoundation.org/show_bug.cgi?id=36709 --- Comment #15 from Kevin Suo --- (In reply to QA Administrators from comment #14) The bug still exists in the most recent version. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124269] The data sheet of the database cannot move the column. Cannot move the bar and insert bar after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=124269 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128169] pizza of death if desktop selected as destination for export/save as to a password protected PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=128169 --- Comment #11 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124269] The data sheet of the database cannot move the column. Cannot move the bar and insert bar after saving
https://bugs.documentfoundation.org/show_bug.cgi?id=124269 --- Comment #3 from QA Administrators --- Dear evan, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128169] pizza of death if desktop selected as destination for export/save as to a password protected PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=128169 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124861] LibreOffice instalation hangs in windows 8.1 64bit
https://bugs.documentfoundation.org/show_bug.cgi?id=124861 --- Comment #2 from QA Administrators --- Dear dilsiam, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124265] After the data table is saved, open the edit and cannot insert the column.
https://bugs.documentfoundation.org/show_bug.cgi?id=124265 --- Comment #3 from QA Administrators --- Dear evan, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127974] Solver Macro cannot solve to a target because there is not suitable API object
https://bugs.documentfoundation.org/show_bug.cgi?id=127974 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124668] Cannot open Libre Office
https://bugs.documentfoundation.org/show_bug.cgi?id=124668 --- Comment #8 from QA Administrators --- Dear Lynn Musgrave, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124265] After the data table is saved, open the edit and cannot insert the column.
https://bugs.documentfoundation.org/show_bug.cgi?id=124265 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 124857] FILEOPEN: Images shift and list design changes
https://bugs.documentfoundation.org/show_bug.cgi?id=124857 --- Comment #3 from QA Administrators --- Dear eng.kim1512, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 112695] impress not listening on bluetooth or tcp 1599 for remote connection
https://bugs.documentfoundation.org/show_bug.cgi?id=112695 --- Comment #6 from QA Administrators --- Dear hgkamath, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 36709] First Line Indent Using Ch (Characters) as Units Won't Change Size as Font Size Grow
https://bugs.documentfoundation.org/show_bug.cgi?id=36709 --- Comment #14 from QA Administrators --- Dear Cheng-Chia Tseng, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 52238] Document templates get formated differently depending on user interface language setting
https://bugs.documentfoundation.org/show_bug.cgi?id=52238 --- Comment #13 from QA Administrators --- Dear Michael P., 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 43848] selecting whole table with merged cells at certain position not possible with draging the mouse
https://bugs.documentfoundation.org/show_bug.cgi?id=43848 --- Comment #16 from QA Administrators --- Dear dE, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45341] Saving document with a input list field as a .doc file makes the input list field read-only
https://bugs.documentfoundation.org/show_bug.cgi?id=45341 --- Comment #15 from QA Administrators --- Dear khagaroth, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 53489] FORMATTING: Doubled line in chart after removing line in represented table
https://bugs.documentfoundation.org/show_bug.cgi?id=53489 --- Comment #7 from QA Administrators --- Dear Samuel V., 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 43107] Regular expression "\n" in replace field inputs "\n" instead of line(paragraph?) break
https://bugs.documentfoundation.org/show_bug.cgi?id=43107 --- Comment #23 from QA Administrators --- Dear Christopher M. Penalver, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120211] Display none para with text:bookmark-start tag displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=120211 --- Comment #5 from QA Administrators --- Dear Antoine POURCHEZ, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 36569] Mouse click into Find Toolbar after undocking will not put caret into toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=36569 --- Comment #14 from QA Administrators --- Dear Ed, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70554] FORMATTING Sub- and superscript format is inherited by new paragraphs
https://bugs.documentfoundation.org/show_bug.cgi?id=70554 --- Comment #11 from QA Administrators --- Dear TJ Corley, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 112687] Presentation annotations are saved with way too many points
https://bugs.documentfoundation.org/show_bug.cgi?id=112687 --- Comment #6 from QA Administrators --- Dear Antonello, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 73494] Font fallback issue with text of mixed directionality in the UI
https://bugs.documentfoundation.org/show_bug.cgi?id=73494 --- Comment #9 from QA Administrators --- Dear Khaled Hosny, 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 49187] Selecting "Sentence case" doesn't correct every sentence in the text (exclamation and question marks work, full stop doesn't)
https://bugs.documentfoundation.org/show_bug.cgi?id=49187 --- Comment #10 from QA Administrators --- Dear Emir Sarı (away), 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 http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128249] Calc does not correctly show some Chinese characters
https://bugs.documentfoundation.org/show_bug.cgi?id=128249 --- Comment #3 from V Stuart Foote --- Can not confirm on Windows 10 Hoime 64-bit en-US (1903) with Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded The Formula input bar uses system font Segoe UI with fall back - it drops the 飏 (yang) fallback and shows an undefined codepoint when it is the last entry on the line. Forcing replacement of system font Segoe UI with Noto Sans CJK TC (from Tools -> Options -> Fonts: Replacement table) fixed the missing fallback glyph, and removes the annoying fallback resize. Otherwise the cells on the sheet pick up their assigned Noto Sans CJK TC and are always fully formed, last glyph or not. Please save a sample .ODS spreadsheet to 'Flat XML ODF Spreadsheet (.fods)' format and attach. But, think the missing glyphs are expected depending on the system locale, and are controllable by forcing a font substitution. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86143] Dragging merged from the corner puts it in a single cell
https://bugs.documentfoundation.org/show_bug.cgi?id=86143 --- Comment #13 from Franklin Weng --- (In reply to karsten.henning from comment #12) > I have reproduced the problem with the same version 6.3.3.1 according to > instructions both under Linux and under Windows. The behavior was identical > and therefore it is not a UX problem. The behavior was identical and therefore it is not an UI problem. What I said UX problem is that, is this behavior intuitive to users? Is this behavior matching what users naturally expect? > The expected behavior is to copy a merged cell in any direction with the > result that at the target also merged cells are created and counted as one > cell. > This is also the behavior in Excel. Right, so I think it is an UX problem. Regardless of what behavior Excel has, it is natural for users to expect this way. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128249] Calc does not correctly show some Chinese characters
https://bugs.documentfoundation.org/show_bug.cgi?id=128249 --- Comment #2 from Owen Parry --- Please note, I priveded the strings as a UTF8 array for YOUR convenience. If I just pasted Chinese characters into the bug report, I have no way of knowing if you can copy them. On your end, use the UTF8 codepoints to convert to readable text and enter them into a cell. Here are the two strings as readable text: 吴珮飏 Pam（吴珮飏） If the font itself was at fault, I would expect to see the box character 100% of the time, that is not the case. As mentioned, either the first, last or all characters are sometimes by the box depending on what is currently selected in the editor. The input bar displays the cells contents correctly, until it is clicked, at which point all characters are converted to boxes. I have just tried with 'Noto Sans CJK'. If the document is saved used Noto, then reopened, the exact same problem exists. All other Chinese characters, as far as I can tell, are displayed correctly. The above combination of 3 characters are causing the problem. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128261] New: The transitions are damaged
https://bugs.documentfoundation.org/show_bug.cgi?id=128261 Bug ID: 128261 Summary: The transitions are damaged Product: LibreOffice Version: 6.2.7.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: joimerjosereyestr...@gmail.com Description: The transitions found at the end of the program menu do not work. This is a problem that comes from previous versions. Steps to Reproduce: 1.Open Impress 2.Open the transitions menu 3.Click on the final group of transitions Actual Results: transitions are damaged Expected Results: To solve it as soon as possible Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128260] New: DOCX import issues from 3-S Thesis Template, most likely sections->Page Styles conversion filter fails somehow!
https://bugs.documentfoundation.org/show_bug.cgi?id=128260 Bug ID: 128260 Summary: DOCX import issues from 3-S Thesis Template, most likely sections->Page Styles conversion filter fails somehow! Product: LibreOffice Version: 6.3.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: e...@sheer.us Description: Using the FormatMyThesis 3-S template dotx file, or files derived from said winword-template, does not import quite right in LibreOffice. Specifically:- (1) the Page-numbers fail after about page 4 of content (chapter 1 starts footnotes etc.) (2) the Mechanic to make sure chapter etc. sections always start on an odd-numbered-page, is not working!. Having communicated with the author, I am now creating this bug-report. The 3 files of interest are:- http://ec2.sheer.us/~enyc/noidx/FMT-3-S-Thesis-Template-v1.0.dotx http://ec2.sheer.us/~enyc/noidx/FMT-3-S-Thesis-Template-v1.0_LO-6.3.2.2.pdf http://ec2.sheer.us/~enyc/noidx/FMT-3-S-Thesis-Template-v1.0_WinWord-2010.pdf So you can access the original dotx, and pdf export examles in any case. Steps to Reproduce: 1. wget and open dotx file from above. 2. Observe page numbers are not working further down the document, as per the LO pdf above. 3. Also Observe the automatically-inserted blank pages are not coming out. Actual Results: As per above page numbers and automatic blank pages are not working right. Expected Results: I would expect a lot of "converted" page styles in a messy fashion, but at least a correctly working imported document. Reproducible: Always User Profile Reset: Yes Additional Info: As above, import of sections and page-level-behavior work fully. Same misbehaviour with various LibreOffice on Linux distros, let alone trying 6.3.2.2 on windows-7-64bit as above!. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128248] Add an easy to use way for alternating cell coloring
https://bugs.documentfoundation.org/show_bug.cgi?id=128248 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WORKSFORME CC||vstuart.fo...@utsa.edu --- Comment #1 from V Stuart Foote --- Already available. 1. Make selection of cells 2. Format -> AutoFormat Styles... 3. select from the Format drop list 4. OK to apply -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128249] Calc does not correctly show some Chinese characters
https://bugs.documentfoundation.org/show_bug.cgi?id=128249 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from V Stuart Foote --- A 2,3 and 4-byte utf-8 coding will not work for direct Unicode input. Calc's =UNICHAR() function can be used against the _decimal_ value of the Unicode point--but is cumbersome compared to the global +x toggle implemented for bug 73691 Convert the input string to utf-16, LibreOffice handles that conversion to Unicode cleanly by prepending "U+", e.g. "U+0050" and then an +x to toggle applied from the end of the string. So, in utf-16 your sample string for Unicode toggle would be: u+0050u+0061u+006du+ff08u+5434u+73eeu+98cfu+ff09 Try that and see if you get better results. Please note that Droid CJK coverage requires an Ascender Pro purchase, not sure the opensource builds included the CJK. The Google Noto Sans CJK successor to Droid is probably a more functional font and is readily available opensource builds. So, if actually using Droid without a CJK locale--you will receive fallback font handling for some font with coverage on system. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128259] New: Formatting Function Conditional in CALC - images
https://bugs.documentfoundation.org/show_bug.cgi?id=128259 Bug ID: 128259 Summary: Formatting Function Conditional in CALC - images Product: LibreOffice Version: 6.3.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: alexmaximiano@gmail.com Created attachment 155158 --> https://bugs.documentfoundation.org/attachment.cgi?id=155158=edit Video showing the error. Hi, I'm using Ubuntu 19.10 and using libreoffice version 6.3.2 (straight from iso). Using conditional image formatting as shown in the video does not change the images and the window is frozen with errors. Following is an attached video showing. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128258] New: Calc feature request: more prominent visual hint for hidden rows or columns
https://bugs.documentfoundation.org/show_bug.cgi?id=128258 Bug ID: 128258 Summary: Calc feature request: more prominent visual hint for hidden rows or columns Product: LibreOffice Version: 6.1.5.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: chameleonsca...@protonmail.com Description: Currently, the only way to tell if rows or columns are hidden is by seeing the thicker separation in the headers. When I work intensively, I often forget that I have hidden cells and this visual hint is too subtle for me to notice it, which leads to me breaking my data and realizing it a while later. Moreover,if for whatever reason I decide to hide the headers themselves, now there's no way to tell if cells are hidden. Steps to Reproduce: Right-clic on a row or column in a header and select "Hide Rows" (or Columns). Actual Results: A thicker line separates the rows between which the hidden one is contained. Expected Results: An efficient solution would be to have an option to display thicker borders where hidden rows or columns are contained (this time on the sheet itself). In addition to that, a color for that thicker line would make it even more prominent and hard to miss. Of course, to ensure one could make this color stand out in any colorized sheet, this color should be changeable in the Preferences. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128257] Bullets Dialog update
https://bugs.documentfoundation.org/show_bug.cgi?id=128257 andreas_k changed: What|Removed |Added CC||kain...@gmail.com Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128257] New: Bullets Dialog update
https://bugs.documentfoundation.org/show_bug.cgi?id=128257 Bug ID: 128257 Summary: Bullets Dialog update Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kain...@gmail.com Created attachment 155157 --> https://bugs.documentfoundation.org/attachment.cgi?id=155157=edit Bullets Dialog 01 The idea is to make an better arrangement for the sd bullet dialog. Top master, Bottom proposal Bullet, Graphic and Number section renewal. Properties are aligned and each section get an alignment too. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #18 from Julien Nabet --- We checked Python but what about Java? On my pc: julien@debianamd:~$ java --version openjdk 11.0.5 2019-10-15 OpenJDK Runtime Environment (build 11.0.5+10-post-Debian-1) OpenJDK 64-Bit Server VM (build 11.0.5+10-post-Debian-1, mixed mode) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions
https://bugs.documentfoundation.org/show_bug.cgi?id=128256 Telesto changed: What|Removed |Added Alias|non-linear, Refactor, |ViewToDevice-Refactor |ViewToDevice| -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions
https://bugs.documentfoundation.org/show_bug.cgi?id=128256 Telesto changed: What|Removed |Added Ever confirmed|0 |1 Alias||Refactor, non-linear, ||ViewToDevice Status|UNCONFIRMED |NEW -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 122713] High CPU usage when viewing spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=122713 Telesto changed: What|Removed |Added Blocks||128256 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128256 [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125677] Radio button selection changed when tabbing into the group.
https://bugs.documentfoundation.org/show_bug.cgi?id=125677 Telesto changed: What|Removed |Added Blocks||128256 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128256 [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125720] Calc: current cell indicator is not following the focused cell (in a particular Form configuration document)
https://bugs.documentfoundation.org/show_bug.cgi?id=125720 Telesto changed: What|Removed |Added Blocks||128256 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128256 [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125700] Radio button selection not changed using arrow keys anymore
https://bugs.documentfoundation.org/show_bug.cgi?id=125700 Telesto changed: What|Removed |Added Blocks||128256 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128256 [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121963] button flashing - mouse wheel zooming breaks
https://bugs.documentfoundation.org/show_bug.cgi?id=121963 Telesto changed: What|Removed |Added Blocks||128256 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128256 [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions
https://bugs.documentfoundation.org/show_bug.cgi?id=128256 Telesto changed: What|Removed |Added Depends on||121963, 125720, 125677, ||125700, 122713 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=121963 [Bug 121963] button flashing - mouse wheel zooming breaks https://bugs.documentfoundation.org/show_bug.cgi?id=122713 [Bug 122713] High CPU usage when viewing spreadsheet https://bugs.documentfoundation.org/show_bug.cgi?id=125677 [Bug 125677] Radio button selection changed when tabbing into the group. https://bugs.documentfoundation.org/show_bug.cgi?id=125700 [Bug 125700] Radio button selection not changed using arrow keys anymore https://bugs.documentfoundation.org/show_bug.cgi?id=125720 [Bug 125720] Calc: current cell indicator is not following the focused cell (in a particular Form configuration document) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions
https://bugs.documentfoundation.org/show_bug.cgi?id=128256 Telesto changed: What|Removed |Added Depends on||127910 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127910 [Bug 127910] main menu and context menus empty when using form elements and OpenGL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127910] main menu and context menus empty when using form elements and OpenGL
https://bugs.documentfoundation.org/show_bug.cgi?id=127910 Telesto changed: What|Removed |Added Blocks||128256 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128256 [Bug 128256] [META] Refactor calc non-linear ViewToDevice transform regressions -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128256] New: [META] Refactor calc non-linear ViewToDevice transform regressions
https://bugs.documentfoundation.org/show_bug.cgi?id=128256 Bug ID: 128256 Summary: [META] Refactor calc non-linear ViewToDevice transform regressions Product: LibreOffice Version: 6.3.0.4 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tele...@surfxs.nl Description: author Armin Le Grand 2018-10-12 11:13:09 +0200 committer Armin Le Grand 2018-11-27 11:33:10 +0100 commit d464d505fbf6e53a38afdd3661d320fac8c760d6 (patch) tree3bf7db8591172bf948198f19d36df5df886486bb parent 3e1e2b6687b0259ae28441cc0d314de0d908776b (diff) Refactor calc non-linear ViewToDevice transform 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220
--- Comment #17 from jul...@palard.fr ---
Still investigating slowly, I bet this is near:
/usr/lib/libreoffice/share/extensions/voikko/pythonpath/PropertyManager.py(83)initialize()
in the call of:
self.__linguPropSet.addPropertyChangeListener("IsSpellWithDigits", self)
Which I bet is a Java function as __linguPropSet is a pyuno object
(com.sun.star.uno.XInterface)0x561ace7484c0{implementationName=com.sun.star.lingu2.LinguProps,
supportedServices={com.sun.star.linguistic2.LinguProperties},
supportedInterfaces={com.sun.star.linguistic2.XLinguProperties,com.sun.star.beans.XFastPropertySet,com.sun.star.beans.XPropertyAccess,com.sun.star.lang.XComponent,com.sun.star.lang.XServiceInfo,com.sun.star.lang.XTypeProvider,com.sun.star.uno.XWeak}}
--
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #16 from jul...@palard.fr --- Yes same version of python3-uno: Installed: 1:6.3.2-1+b1 thanks for trying hard to reproduce, I appreciate it. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 Julien Nabet changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #15 from Julien Nabet --- I noticed the use of python3-uno Package: python3-uno Source: libreoffice (1:6.3.2-1) Version: 1:6.3.2-1+b1 but I suppose you've got the same version. I don't have more questions, so I'll put this back to UNCONFIRMED. I must recognize I'm stuck. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127494] Enhancement request: shortcut for "Search" line in Help menu
https://bugs.documentfoundation.org/show_bug.cgi?id=127494 --- Comment #3 from V Stuart Foote --- Implicit in implementation of enhancement for bug 91874 would be ability to assign shortcut to the search bar for keyboard only completion without need for mouse selection. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128255] No data collection without express, informed, meaningful user consent.
https://bugs.documentfoundation.org/show_bug.cgi?id=128255 V Stuart Foote changed: What|Removed |Added Resolution|--- |MOVED CC||c...@nouenoff.nl, ||jbfa...@libreoffice.org, ||ke...@collabora.com, ||marina.latini@libreoffice.o ||rg, ||markus.mohrhard@googlemail. ||com, ||michael.me...@collabora.com ||, vstuart.fo...@utsa.edu Status|UNCONFIRMED |RESOLVED --- Comment #1 from V Stuart Foote --- User is prompted on Crash recovery if they explicitly want to submit the Breakpad generated minidump crash report. No personally identifiable details are included beyond the cURL post details of the originating IP. User has explicit control over "Collect usage data and send it to The Document Foundation"--it is disabled by default on installation. It is only enabled by user action in the Tools -> Options -> LibreOffice General panel, or by setting an environment variable "LO_COLLECT_USAGE" true. There is no personally identifiable information beyond source IP and system network name, otherwise it is just tallys of command/control usage per document per session. IMHO the user is sufficiently advised, abd providing more complex user notification in the GUI is _visual noise_. IMHO => WF Otherwise, TDF Project and LibreOffice privacy statements (which admittedly do not address crash reporintg and usage data) are the purview of the TDF Board and their legal advisers. Discussion on appropriate ML no in the BZ --> MOVED For BoD -- if you take this up could you provide a suitable link to the discussion. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #14 from jul...@palard.fr --- OK, I may have something, but yet I'm not fluent with this Java/Python interaction. Right before the crash I see: > /usr/lib/python3/dist-packages/unohelper.py(252)getTypes()->( instanc...INTERFACE')>)>, )>, instanc...INTERFACE')>)>) -> return _unohelper_getHandle( self ) (Pdb) l 247 _g_typeTable[self.__class__] = ret 248 return ret 249 250 class Base(XTypeProvider): 251 def getTypes( self ): 252 -> return _unohelper_getHandle( self ) 253 def getImplementationId(self): 254 return () 255 256 class CurrentContext(XCurrentContext, Base ): 257 """a current context implementation, which first does a lookup in the given (Pdb) p _unohelper_getHandle( self ) ()>, )>, )>) (Pdb) n Fatal Python error: Python memory allocator called without holding the GIL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91874] A Search by function or keyword over main menu-- similar to SpotLight, Tell Me, or Ubuntu's HUD but native for LO GUI
https://bugs.documentfoundation.org/show_bug.cgi?id=91874 --- Comment #30 from maryline.lato...@gmail.com --- Keep the smart user’s point of view in mind please. The aim of my original 127494 enhancements suggestion that was sadly marked as duplicate of this one is to use the mouse LESS and keep both your hands on the keyboard for efficiency. As it was possible with older versions. Remember? SAVE THE KEYBOARD SHORTCUTS! Don’t imitate Word’s mouse only interface. Please. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #13 from jul...@palard.fr --- Hum no forget the last one about the traceback, it looks like I introduced it myself while trying to debug ... -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127494] Enhancement request: shortcut for "Search" line in Help menu
https://bugs.documentfoundation.org/show_bug.cgi?id=127494 --- Comment #2 from maryline.lato...@gmail.com --- Sad it’s been marked as a duplicate. The aim of this enhancement suggestion is to use the mouse LESS and keep both your hands on the keyboard. As it was possible with older versions. SAVE THE KEYBOARD SHORTCUTS! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #12 from jul...@palard.fr --- > Could you check these libs: Yes: $ apt-cache policy unoconv uno-libs3 ure unoconv: Installed: (none) Candidate: 0.7-1.1 Version table: 0.7-1.1 990 990 https://deb.debian.org/debian bullseye/main amd64 Packages 500 https://deb.debian.org/debian sid/main amd64 Packages uno-libs3: Installed: 6.3.2-1+b1 Candidate: 6.3.2-1+b1 Version table: 6.3.3~rc1-1 500 500 https://deb.debian.org/debian sid/main amd64 Packages *** 6.3.2-1+b1 990 990 https://deb.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status ure: Installed: 6.3.2-1+b1 Candidate: 6.3.2-1+b1 Version table: 6.3.3~rc1-1 500 500 https://deb.debian.org/debian sid/main amd64 Packages *** 6.3.2-1+b1 990 990 https://deb.debian.org/debian bullseye/main amd64 Packages 100 /var/lib/dpkg/status Oh, while I'm in this function, I can see the traceback being pretty printed, if it helps: File "/usr/lib/libreoffice/program/pythonloader.py", line 136, in activate mod = self.getModuleFromUrl( locationUrl ) File "/usr/lib/libreoffice/program/pythonloader.py", line 104, in getModuleFromUrl exec(codeobject, mod.__dict__) File "/usr/lib/libreoffice/share/extensions/voikko/lovoikko.py", line 15, in from SettingsEventHandler import SettingsEventHandler File "/usr/lib/python3/dist-packages/uno.py", line 359, in _uno_import return _builtin_import(name, *optargs, **kwargs) File "/usr/lib/libreoffice/share/extensions/voikko/pythonpath/SettingsEventHandler.py", line 18, in from PropertyManager import PropertyManager File "/usr/lib/python3/dist-packages/uno.py", line 359, in _uno_import return _builtin_import(name, *optargs, **kwargs) File "/usr/lib/libreoffice/share/extensions/voikko/pythonpath/PropertyManager.py", line 18, in from VoikkoHandlePool import VoikkoHandlePool File "/usr/lib/python3/dist-packages/uno.py", line 359, in _uno_import return _builtin_import(name, *optargs, **kwargs) File "/usr/lib/libreoffice/share/extensions/voikko/pythonpath/VoikkoHandlePool.py", line 15, in from libvoikko import Voikko, VoikkoException File "/usr/lib/python3/dist-packages/uno.py", line 359, in _uno_import return _builtin_import(name, *optargs, **kwargs) sadly I don't see the exception being handled, the only parameter is the traceback. I don't know if I can gather information about the running Java process at the moment of the exception (I'm more fluent in debugging Python than debugging Java). -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #11 from Julien Nabet --- Could you check these libs: unoconv uno-libs3 ure ? Here what I got, I expect you got the same but since you also got unstable. root@debianamd:~# apt-cache policy unoconv unoconv: Installé : (aucun) Candidat : 0.7-1.1 Table de version : 0.7-1.1 500 500 http://ftp.fr.debian.org/debian stable/main amd64 Packages 500 http://ftp.fr.debian.org/debian testing/main amd64 Packages root@debianamd:~# apt-cache policy uno-libs3 uno-libs3: Installé : 6.3.2-1+b1 Candidat : 6.3.2-1+b1 Table de version : *** 6.3.2-1+b1 500 500 http://ftp.fr.debian.org/debian testing/main amd64 Packages 100 /var/lib/dpkg/status 6.1.5-3+deb10u3 500 500 http://ftp.fr.debian.org/debian stable/main amd64 Packages root@debianamd:~# apt-cache policy ure ure: Installé : 6.3.2-1+b1 Candidat : 6.3.2-1+b1 Table de version : *** 6.3.2-1+b1 500 500 http://ftp.fr.debian.org/debian testing/main amd64 Packages 100 /var/lib/dpkg/status 6.1.5-3+deb10u3 500 500 http://ftp.fr.debian.org/debian stable/main amd64 Packages -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #10 from jul...@palard.fr --- Looks like the error happen really near some: > /usr/lib/python3/dist-packages/uno.py(562)_uno_extract_printable_stacktrace() -> return ''.join(traceback.format_tb(trace)) probably right after. This looks called directly from Java (I have no stacktrace), the function runs well, and right after the return I have the crash. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #9 from jul...@palard.fr --- So my locales: LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL=en_US.utf8 > Did you install any specific extensions? No, it's a brand new laptop, freshly installed. > Also when you indicated you uninstalled LO, did you include the profile in > ~/.config/libreoffice ? No but rm -fr it does not help (still crashes). Tried: $ sudo apt purge python3-libvoikko [sudo] password for mdk: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: libreoffice-voikko* python3-libvoikko* 0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded. After this operation, 168 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 328933 files and directories currently installed.) Removing libreoffice-voikko (5.0-3+b1) ... Removing python3-libvoikko (4.2-2) ... Processing triggers for libreoffice-common (1:6.3.2-1) ... Then no crash. Then: $ sudo apt install libreoffice-voikko Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: python3-libvoikko The following NEW packages will be installed: libreoffice-voikko python3-libvoikko 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Need to get 50.5 kB of archives. After this operation, 168 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 https://cdn-aws.deb.debian.org/debian bullseye/main amd64 python3-libvoikko all 4.2-2 [27.1 kB] Get:2 https://cdn-aws.deb.debian.org/debian bullseye/main amd64 libreoffice-voikko amd64 5.0-3+b1 [23.4 kB] Fetched 50.5 kB in 2s (31.8 kB/s) Selecting previously unselected package python3-libvoikko. (Reading database ... 328897 files and directories currently installed.) Preparing to unpack .../python3-libvoikko_4.2-2_all.deb ... Unpacking python3-libvoikko (4.2-2) ... Selecting previously unselected package libreoffice-voikko. Preparing to unpack .../libreoffice-voikko_5.0-3+b1_amd64.deb ... Unpacking libreoffice-voikko (5.0-3+b1) ... Setting up python3-libvoikko (4.2-2) ... Setting up libreoffice-voikko (5.0-3+b1) ... Processing triggers for libreoffice-common (1:6.3.2-1) ... mdk@seraph$ rm -fr ~/.config/libreoffice/ mdk@seraph$ libreoffice # Then click on "Writer Document" Fatal Python error: Python memory allocator called without holding the GIL > what desktop do you use? Personally, I use gtk3. I don't really understand this question, I'll try to answer, tell me if I'm out of scope: I'm using i3wm, started by lightdm, on top of Xorg. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 97362] Convert Java complex tests to Python
https://bugs.documentfoundation.org/show_bug.cgi?id=97362 Guillaume Monzerol changed: What|Removed |Added Assignee|guillaume.monze...@gmail.co |libreoffice-b...@lists.free |m |desktop.org -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #8 from Julien Nabet --- Also when you indicated you uninstalled LO, did you include the profile in ~/.config/libreoffice ? Did you install any specific extensions? what desktop do you use? Personally, I use gtk3. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #7 from Julien Nabet --- I installed libenchant-voikko which wasn't present, still no crash. What's your localization? (UI + local parameters) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117595] UI hangs on Tools -> Options (or Alt-F12)
https://bugs.documentfoundation.org/show_bug.cgi?id=117595 Timur changed: What|Removed |Added Resolution|WORKSFORME |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #6 from jul...@palard.fr --- In my case, opening LO and just clicking "Writer Document" is enough to crash. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220
--- Comment #5 from jul...@palard.fr ---
If it can help:
here's my apt list --installed | grep libreoffice:
libreoffice-base-core/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-base-drivers/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-base/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-calc/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-common/testing,now 1:6.3.2-1 all [installed,automatic]
libreoffice-core/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-draw/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-gnome/testing,now 1:6.3.2-1+b1 amd64 [installed]
libreoffice-gtk3/testing,now 1:6.3.2-1+b1 amd64 [installed]
libreoffice-impress/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-java-common/testing,now 1:6.3.2-1 all [installed,automatic]
libreoffice-math/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-nlpsolver/testing,now 0.9+LibO6.3.2-1 all [installed,automatic]
libreoffice-report-builder-bin/testing,now 1:6.3.2-1+b1 amd64
[installed,automatic]
libreoffice-report-builder/testing,now 1:6.3.2-1 all [installed,automatic]
libreoffice-script-provider-bsh/testing,now 1:6.3.2-1 all [installed,automatic]
libreoffice-script-provider-js/testing,now 1:6.3.2-1 all [installed,automatic]
libreoffice-script-provider-python/testing,now 1:6.3.2-1 all
[installed,automatic]
libreoffice-sdbc-firebird/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-sdbc-mysql/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice-sdbc-postgresql/testing,now 1:6.3.2-1+b1 amd64
[installed,automatic]
libreoffice-style-colibre/testing,now 1:6.3.2-1 all [installed,automatic]
libreoffice-style-elementary/testing,now 1:6.3.2-1 all [installed]
libreoffice-style-tango/testing,now 1:6.3.2-1 all [installed,automatic]
libreoffice-voikko/testing,unstable,now 5.0-3+b1 amd64 [installed]
libreoffice-wiki-publisher/testing,now 1.2.0+LibO6.3.2-1 all
[installed,automatic]
libreoffice-writer/testing,now 1:6.3.2-1+b1 amd64 [installed,automatic]
libreoffice/testing,now 1:6.3.2-1+b1 amd64 [installed]
mdk@seraph$ which python3
/usr/bin/python3
mdk@seraph$ dpkg -S $(which python3)
python3-minimal: /usr/bin/python3
mdk@seraph$ apt-cache policy python3-minimal
python3-minimal:
Installed: 3.7.5-1
Candidate: 3.7.5-1
Version table:
*** 3.7.5-1 990
990 https://deb.debian.org/debian bullseye/main amd64 Packages
500 https://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
According to strace, it uses this Python, not Python 2, I see:
$ grep -i python --color /tmp/libreoffice.strace
14771 openat(AT_FDCWD,
"/usr/lib/libreoffice/program/services/scriptproviderforpython.rdb", O_RDONLY)
= 7
14771 openat(AT_FDCWD, "/usr/lib/libreoffice/program/libpythonloaderlo.so",
O_RDONLY|O_CLOEXEC) = 22
14771 openat(AT_FDCWD, "/usr/lib/libreoffice/program/libpython3.7m.so.1.0",
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
14771 openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libpython3.7m.so.1.0",
O_RDONLY|O_CLOEXEC) = 22
14771 access("/usr/lib/libreoffice/program/pythonloader.unorc", F_OK) = 0
14771 openat(AT_FDCWD, "/usr/lib/libreoffice/program/pythonloader.unorc",
O_RDONLY) = 22
[...]
14771 stat("/usr/lib/python3/dist-packages/libvoikko.py",
{st_mode=S_IFREG|0644, st_size=33294, ...}) = 0
Also:
$ apt list --installed | grep voikko
libenchant-voikko/testing,unstable,now 1.6.0-11.3 amd64
[installed,automatic]
libreoffice-voikko/testing,unstable,now 5.0-3+b1 amd64 [installed]
libvoikko1/testing,unstable,now 4.2-2 amd64 [installed,automatic]
python3-libvoikko/testing,unstable,now 4.2-2 all [installed,automatic]
voikko-fi/testing,unstable,now 2.3-1 amd64 [installed,automatic]
--
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127910] main menu and context menus empty when using form elements and OpenGL
https://bugs.documentfoundation.org/show_bug.cgi?id=127910 V Stuart Foote changed: What|Removed |Added CC||martin.wieb...@gmx.de --- Comment #14 from V Stuart Foote --- *** Bug 128253 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128253] Menu disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=128253 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||vstuart.fo...@utsa.edu --- Comment #2 from V Stuart Foote --- You look to be on Windows with OpenGL rendering enabled, disable OpenGL (Tools -> Options -> View dialog) that will work around the visual glitch. *** This bug has been marked as a duplicate of bug 127910 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 98255] Excel keyboard shortcut bindings for Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=98255 V Stuart Foote changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #11 from V Stuart Foote --- *** Bug 128247 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128247] Include a template for MS Office shortcuts to ease the transition to LO
https://bugs.documentfoundation.org/show_bug.cgi?id=128247 V Stuart Foote changed: What|Removed |Added CC||vstuart.fo...@utsa.edu Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from V Stuart Foote --- While scope here is entire suite, bug 98255 is already open against Calc where we already provide 'legacy' mode (Tools -> Options -> Calc -> Combatibility : 'Key Bindings' drop list. Low hanging fruit is for Calc becuase of that existing framework. But potential for 'theming'/'skinning' other modules in addition to Calc against keyboard shortcuts of other popular productivity and DTP programs. *** This bug has been marked as a duplicate of bug 98255 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 50916] Allow more than 1024 columns in calc
https://bugs.documentfoundation.org/show_bug.cgi?id=50916 --- Comment #102 from Commit Notification --- Michael Meeks committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/2571a11aeb0bdca20242caa5c96f0a5b3ea5db90 sc: rowcol: tdf#50916 convert ucalc test, and docfunc. It will be available in 6.4.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 126293] Save icon changes size when document gets modified
https://bugs.documentfoundation.org/show_bug.cgi?id=126293 --- Comment #14 from Michael Meeks --- Sure - why not if someone wants to test & maintain that, I don't have time personally, sorry ! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 91874] A Search by function or keyword over main menu-- similar to SpotLight, Tell Me, or Ubuntu's HUD but native for LO GUI
https://bugs.documentfoundation.org/show_bug.cgi?id=91874 V Stuart Foote changed: What|Removed |Added CC||eido.ask...@gmail.com --- Comment #29 from V Stuart Foote --- *** Bug 128242 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128242] Add support for execution of commands by typing the corresponding command name
https://bugs.documentfoundation.org/show_bug.cgi?id=128242 V Stuart Foote changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||vstuart.fo...@utsa.edu --- Comment #2 from V Stuart Foote --- *** This bug has been marked as a duplicate of bug 91874 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127720] FILEOPEN PPTX Y error bars gone from XY Scatter chart
https://bugs.documentfoundation.org/show_bug.cgi?id=127720 NISZ LibreOffice Team changed: What|Removed |Added Summary|FILEOPEN PPTX Whiskers gone |FILEOPEN PPTX Y error bars |from boxes in chart |gone from XY Scatter chart -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128255] New: No data collection without express, informed, meaningful user consent.
https://bugs.documentfoundation.org/show_bug.cgi?id=128255 Bug ID: 128255 Summary: No data collection without express, informed, meaningful user consent. Product: LibreOffice Version: 6.3.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoffic...@sfina.com Description: This is a collateral to Bug 128232. Bug 128232 is open source working at its best, with a fix within less than 24 hours of the bug report. However, in the process of reporting the bug I learned that LibreOffice called home (crashreport.libreoffice.org). I understand it is with good intentions. I am still trying to figure out the details. I believe that telemetry without consent is not the Right Thing to do. Please help me understand, and please help me help the Document Foundation / LibreOffice become more respectful of data privacy. Steps to Reproduce: 1. crash LibreOffice 2. monitor your internet connection Actual Results: LibreOffice calls home without warning. Expected Results: LibreOffice should ask for user consent, or crash silently. Reproducible: Always User Profile Reset: No Additional Info: User consent has to be (A) express; (B) informed; (C) meaningful. (A) Express. Put a dialogue in front of the user every time consent should be sought. Consent for telemetry at installation is good. If consent was granted the first time, repeating the request on significant changes and upgrades as a reminder of the original consent is better. For the user in a sensitive environment (lawyers, dissident journalist, HR employees, any person that requires confidentiality for whatever reasons) asking to reaffirm consent at every start of the application makes sense. Ideally, the express consent should be time-limited and revert back to no data leak permitted, with the choices: (a) until the next time the user restarts LibreOffice; (b) until the next LibreOffice upgrade/change; (c) for a fixed (arbitrary) time period of a year; or (d) forever. (B) informed. describe in clear words what triggers telemetry, and what kind of information is sent. To the user, a summary with links to documentation on the Document Foundation's webpage should be sufficient. From that webpage, link further down into the exact points in the code / repository where the data is collected and where the telemetry is triggered. When I started researching crashreport.libreoffice.org, I came across https://github.com/mmohrhard/crash -- too much into details for me to understand what is going on. I also came across conspiracy theories that are even less useful. The software publisher should fill the void and prevent it from being filled by conspiracy theories. (C) meaningful. even after a user has expressly consented, there are circumstances under which refreshing the consent makes sense. For example, when the data leaked out of the user's control contains information from the documents being edited, the user may need to consider the nature of the document being edited to arrive to a meaningful consent. A user consenting to telemetry while editing a party invitation can reasonably deny consent when editing a list of employees with salaries and other confidential data. Please build software that can be trusted. Thanks for listening. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 75057] [META] OOXML Chart object issues
https://bugs.documentfoundation.org/show_bug.cgi?id=75057 NISZ LibreOffice Team changed: What|Removed |Added Depends on||127720 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127720 [Bug 127720] FILEOPEN PPTX Whiskers gone from boxes in chart -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108226] [META] PPTX (OOXML) bug tracker
https://bugs.documentfoundation.org/show_bug.cgi?id=108226 NISZ LibreOffice Team changed: What|Removed |Added Depends on|127720 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127720 [Bug 127720] FILEOPEN PPTX Whiskers gone from boxes in chart -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127720] FILEOPEN PPTX Whiskers gone from boxes in chart
https://bugs.documentfoundation.org/show_bug.cgi?id=127720 NISZ LibreOffice Team changed: What|Removed |Added Blocks|108226 |75057 --- Comment #2 from NISZ LibreOffice Team --- For the record, the "whiskers" are Y error bars. The chart is a XY (Scatter) type chart. Opening it and checking the "Select Chart Element" box shows there is no "Y Error Bars" component for any data series. However changing the chart type to Line in PP and opening the file in Impress, there is an "Y Error Bars" component for the Series1 data series and the error bars also correctly show up on the chart. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=75057 [Bug 75057] [META] OOXML Chart object issues https://bugs.documentfoundation.org/show_bug.cgi?id=108226 [Bug 108226] [META] PPTX (OOXML) bug tracker -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 59323] Impress conversion to PPTX doesn't save (header and footer) fields - with sample or steps in Comment 7
https://bugs.documentfoundation.org/show_bug.cgi?id=59323 Timur changed: What|Removed |Added Component|Writer |Impress -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128254] Menu disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=128254 Martin changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Martin --- *** This bug has been marked as a duplicate of bug 128253 *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128253] Menu disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=128253 --- Comment #1 from Martin --- *** Bug 128254 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128254] New: Menu disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=128254 Bug ID: 128254 Summary: Menu disabled Product: LibreOffice Version: 6.3.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: martin.wieb...@gmx.de Add Buttons (via "Formular-Steuerelemente"). After that all Menues are grey ! Funny -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128253] New: Menu disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=128253 Bug ID: 128253 Summary: Menu disabled Product: LibreOffice Version: 6.3.2.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: martin.wieb...@gmx.de Created attachment 155154 --> https://bugs.documentfoundation.org/attachment.cgi?id=155154=edit grey Menu Add Buttons (via "Formular-Steuerelemente"). After that all Menues are grey ! Funny -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120679] [META] Labels and Business Cards issues
https://bugs.documentfoundation.org/show_bug.cgi?id=120679 Bug 120679 depends on bug 61030, which changed state. Bug 61030 Summary: FORMATTING: Synchronize for Business Cards has no effect https://bugs.documentfoundation.org/show_bug.cgi?id=61030 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 61030] FORMATTING: Synchronize for Business Cards has no effect
https://bugs.documentfoundation.org/show_bug.cgi?id=61030 Laurent BP changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #11 from Laurent BP --- 1. File > New > Business Cards 2. Click New document 3. Enter text 4. Click "Synchronize" button Cards are populated as expected. Version: 6.2.6.2 Build ID: 684e730861356e74889dfe6dbddd3562aae2e6ad Threads CPU : 8; OS : Linux 5.0; UI Render : par défaut; VCL: gtk3; Locale : fr-FR (fr_FR.UTF-8); Langue IHM : fr-FR Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118034] Import of xslx chart has wrong position and wrong precision of trendline equation
https://bugs.documentfoundation.org/show_bug.cgi?id=118034 NISZ LibreOffice Team changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=55 ||204 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 55204] FILEOPEN PPTX Equation in chart displayed incorrectly (see comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=55204 NISZ LibreOffice Team changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||8034 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 86143] Dragging merged from the corner puts it in a single cell
https://bugs.documentfoundation.org/show_bug.cgi?id=86143 --- Comment #12 from karsten.henn...@gmx.de --- I have reproduced the problem with the same version 6.3.3.1 according to instructions both under Linux and under Windows. The behavior was identical and therefore it is not a UX problem. The expected behavior is to copy a merged cell in any direction with the result that at the target also merged cells are created and counted as one cell. This is also the behavior in Excel. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128006] Macro warning dialog is prompted on every function or sub call
https://bugs.documentfoundation.org/show_bug.cgi?id=128006 --- Comment #7 from Pedro --- Thanks Oliver. I assume that there is no need to declare the database files to the trusted zone since the macros are already in the trusted zone by default. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128241] Crash when opening print dialog (gtk3 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=128241 Caolán McNamara changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |caol...@redhat.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 --- Comment #4 from Julien Nabet --- Julien: I type some text and indicated it was finnish. Then I call spell checking, still no crash -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128220] Fatal Python error: Python memory allocator called without holding the GIL
https://bugs.documentfoundation.org/show_bug.cgi?id=128220 Julien Nabet changed: What|Removed |Added CC||r...@debian.org, ||timo.jyrinki+libreoffice@ik ||i.fi --- Comment #3 from Julien Nabet --- Timo/Rene: thought you might be interested in this one On pc Debian testing x86-64 updated today, I installed libreoffice-voikko root@debianamd:~# apt-cache show libreoffice-voikko Package: libreoffice-voikko Source: libreoffice-voikko (5.0-3) Version: 5.0-3+b1 which installed: root@debianamd:~# apt-cache show python3-libvoikko Package: python3-libvoikko Source: libvoikko Version: 4.2-2 I started LO and had startcenter, then I click on Writer icon, no crash here. which python: /usr/bin/python lrwxrwxrwx 1 root root 7 oct. 10 13:32 /usr/bin/python -> python2 julien@debianamd:~$ which python3 /usr/bin/python3 lrwxrwxrwx 1 root root 9 oct. 2 14:31 /usr/bin/python3 -> python3.7 julien@debianamd:~$ apt-cache show python2 Package: python2 Source: python-defaults Version: 2.7.17-1 Package: python3 Source: python3-defaults Version: 3.7.5-1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
