[Libreoffice-bugs] [Bug 143806] Writer opens DOCX with slightly higher text spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=143806 --- Comment #11 from Justin L --- (In reply to Meitar Bruner from comment #8) > Do you know why this is happening? > A solution for this could really help! 1.) Do you have the Calibri font installed on your LibreOffice system? Obviously if all the fonts used aren't installed, then spacing can be different. (I too don't own Calibri, so I don't know if that would actually help, but this seems the most likely reason.) 2.) Normally the Heading styles have turned on the "keep with next paragraph" property, so that the document knows they should not be orphaned on a previous page. (That is much better than depending on "hitting enter to get the layout you want".) 3.) And of course the advice you didn't want is the best one. You NEVER start a new page by hitting Enter 20 times. (Why would you expect good results from bad document design?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70142] Make numbering, fields and other dynamic text searchable
https://bugs.documentfoundation.org/show_bug.cgi?id=70142 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||7737 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137737] REPLACE not working if there is a footnote or endnote anchor at end of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=137737
Mike Kaganski changed:
What|Removed |Added
Keywords||needsUXEval
CC||er...@redhat.com
See Also||https://bugs.documentfounda
||tion.org/show_bug.cgi?id=70
||142
--- Comment #22 from Mike Kaganski ---
(In reply to Justin L from comment #21)
> This is difficult because we have two very real situations here. The most
> common one would be OPs - where LO implementation specifics are not cared
> about, and the regex is only concerned about the "text". So I think this is
> the one that needs the most focus, even though regex is a "pro user" feature.
>
> The second would be someone who is actually searching for footnote markers
> etc. But that "developer class" level of user will be very rare.
Thank you!
Let me mention tdf#70142 for some context here. People *in general* expect that
what they *see* on screen is searchable (which includes fields, numbering,
etc.); and in this regard, footnote anchor at lease should *participate* in
search (even if its character is not (yet) searchable).
OTOH, making dynamic text inside special objects searchable has some drawback:
e.g., replacing would be impossible when find-and-replace searches inside
fields (how would it replace inside or across boundaries of a field?).
So conceptually, there might be two modes for find: "normal" search, and
"search inside fields" (the latter one disabling replace).
But anyway, recognizing special objects as parts of text (even if just as
"control characters" in normal mode) would change workflow, but not disallow
things (possibly just require somewhat more complex expressions - consider
comment 19). I suppose that separating "normal power users" from "advanced
power users" when talking about regexes is too much, and IMO just mentioning in
the release notes (and related help page) that now the selected special objects
(footnote anchors) match [\p{Control}] would be enough - this adds flexibility.
OTOH, things like floating object anchors or reference or index entry are
completely "metadata". We need to modify the code to remove those objects from
the search string completely (which should be possible IMO, just needs more
work; and doing that would enable tdf#70142, because that way, we would be able
to replace the special characters *universally* including in the middle of the
string).
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143725] Unable to register/login to ask.libreoffice
https://bugs.documentfoundation.org/show_bug.cgi?id=143725 Aleksandra changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |MOVED --- Comment #1 from Aleksandra --- Hello k...@kirk-ward.com! Please write about your problem here: http://redmine.documentfoundation.org Thank you so much! Best wishes, Aleksandra -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143806] Writer opens DOCX with slightly higher text spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=143806 Justin L changed: What|Removed |Added Attachment #174188|text/plain |application/vnd.openxmlform mime type||ats-officedocument.wordproc ||essingml.document Attachment #174188|1 |0 is patch|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109018] Character border conflict with hyphens
https://bugs.documentfoundation.org/show_bug.cgi?id=109018 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #7 from BogdanB --- Aslo in Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: fbe183bbb05220a4ccc51952445b1797bb498403 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 shodgman changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #10 from shodgman --- I was Too Hasty - Still getting this behaviour in 7.2.0.4 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131531] FILESAVE ODT->DOCX: Header height of first page is not reserved
https://bugs.documentfoundation.org/show_bug.cgi?id=131531 Justin L changed: What|Removed |Added CC||jl...@mail.com Summary|FILESAVE DOCX: Header |FILESAVE ODT->DOCX: Header |height of first page is not |height of first page is not |reserved|reserved --- Comment #9 from Justin L --- My opinion (without looking into the specific issue) is that when emulation needs to happen and there is not a clear "right" approach, then just leave things as they other. Otherwise you will likely cause a regression for someone else. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137737] REPLACE not working if there is a footnote or endnote anchor at end of paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=137737 --- Comment #21 from Justin L --- (In reply to Mike Kaganski from comment #20) > Please reply what you think specifically about #1 here. Note again, that > this would fix it in a very different way compared to what OP wanted. This is difficult because we have two very real situations here. The most common one would be OPs - where LO implementation specifics are not cared about, and the regex is only concerned about the "text". So I think this is the one that needs the most focus, even though regex is a "pro user" feature. The second would be someone who is actually searching for footnote markers etc. But that "developer class" level of user will be very rare. I personally expect that find/replace would ignore all of these internal things - and that is obviously how previous implementers also viewed it. (And they also acknowledged it is basically impossible to avoid mid-paragraph.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144072] LibreofficeBase crashed when 2 fields selected in report builder from different sections and width is adjusted 2nd time
https://bugs.documentfoundation.org/show_bug.cgi?id=144072 shodgman changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #9 from shodgman --- Just downloaded 7.2.0.4 (Windows 10) and cannot reproduce the fault. Seeing different behaviour now. Thanks everyone for the support and for chasing it up. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143764] bump scroll too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=143764 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138990] ODBC - LO, LO Vanilla, Collabora Office fail to retrieve ODBC datasources on M1 Apple Silicon
https://bugs.documentfoundation.org/show_bug.cgi?id=138990 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143835] [UI]/[EDITING] Formula bar only accepts dead key inputs when typing in it for the first time
https://bugs.documentfoundation.org/show_bug.cgi?id=143835 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143730] Spell Checker giving wrong spelling
https://bugs.documentfoundation.org/show_bug.cgi?id=143730 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141337] Python doc.Sheets.copyByName(existingname, newname, position) does not update references in chart when copying sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=141337 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143830] LOOL: SIGABRT trying to spawn spare kits
https://bugs.documentfoundation.org/show_bug.cgi?id=143830 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143832] Can not generate pycache (.pyc) files on Windows as non-admin accounts
https://bugs.documentfoundation.org/show_bug.cgi?id=143832 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139545] Nimbus Roman No9 L Bold font (otf fomat) not displayed correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=139545 --- Comment #4 from QA Administrators --- Dear donotspam, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144033] Libreoffice (Calc) rendering very slow on GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=144033 --- 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] [Bug 144033] Libreoffice (Calc) rendering very slow on GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=144033 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139853] libreoffice Calc Vlookup Error
https://bugs.documentfoundation.org/show_bug.cgi?id=139853 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139853] libreoffice Calc Vlookup Error
https://bugs.documentfoundation.org/show_bug.cgi?id=139853 --- Comment #7 from QA Administrators --- Dear peter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139545] Nimbus Roman No9 L Bold font (otf fomat) not displayed correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=139545 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134967] LibreOffice Writer causes Ubuntu system forced logout when trying to handle multiple imported screenshots
https://bugs.documentfoundation.org/show_bug.cgi?id=134967 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 99514] FILEOPEN .xlsm error 37 times: BASIC runtime error. '423' Value2
https://bugs.documentfoundation.org/show_bug.cgi?id=99514 --- Comment #6 from QA Administrators --- Dear Bruce Blodgett, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134967] LibreOffice Writer causes Ubuntu system forced logout when trying to handle multiple imported screenshots
https://bugs.documentfoundation.org/show_bug.cgi?id=134967 --- Comment #3 from QA Administrators --- Dear trumpetguy314, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140692] not printing multiple copies
https://bugs.documentfoundation.org/show_bug.cgi?id=140692 --- Comment #2 from QA Administrators --- Dear Blake, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95928] print preview upside down in case of Visio object
https://bugs.documentfoundation.org/show_bug.cgi?id=95928 --- Comment #9 from QA Administrators --- Dear Winfried Donkers, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140244] Text distribution with 'anchor to character' off on file open with columns on file open (even looked good at save)
https://bugs.documentfoundation.org/show_bug.cgi?id=140244 --- Comment #4 from QA Administrators --- Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140614] polices instables
https://bugs.documentfoundation.org/show_bug.cgi?id=140614 --- Comment #2 from QA Administrators --- Dear eric.betheuil, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 73523] bitmaps embedded in a visio file are imported as black boxes
https://bugs.documentfoundation.org/show_bug.cgi?id=73523 --- Comment #12 from QA Administrators --- Dear Maxim Ganetsky, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 73515] EDITING: Legend information disappears after document reload
https://bugs.documentfoundation.org/show_bug.cgi?id=73515 --- Comment #12 from QA Administrators --- Dear opensuse.lietuviu.kalba, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72985] EDITING: mismanagement of the "Object with no fill and no line" Images style
https://bugs.documentfoundation.org/show_bug.cgi?id=72985 --- Comment #8 from QA Administrators --- Dear pierre-yves samyn, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 69217] When modified Basic code, closing LibreOffice does not ask for confirmation, nor to save modified code
https://bugs.documentfoundation.org/show_bug.cgi?id=69217 --- Comment #11 from QA Administrators --- Dear Lionel Elie Mamane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 70379] Cannot resize columns with protected cells / Calc does not respect users' permissions
https://bugs.documentfoundation.org/show_bug.cgi?id=70379 --- Comment #11 from QA Administrators --- Dear Roman Polach, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63799] FORMATTING: Distorted stencil on copy & Paste from Visio 2010
https://bugs.documentfoundation.org/show_bug.cgi?id=63799 --- Comment #7 from QA Administrators --- Dear Malte S. Stretz, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 63130] FILESAVE Libreoffice has stopped working when saving or working with large Visio 2003 Drawing
https://bugs.documentfoundation.org/show_bug.cgi?id=63130 --- Comment #18 from QA Administrators --- Dear Jeff L., To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127188] FORMATTING adding decimal places changes format
https://bugs.documentfoundation.org/show_bug.cgi?id=127188 --- Comment #2 from QA Administrators --- Dear bruce, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104832] CRASH when selecting OLE (Visio?) object (in a DOC file)
https://bugs.documentfoundation.org/show_bug.cgi?id=104832 --- Comment #13 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142943] Can't change paragraph styles by double-clicking a style on sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=142943 Jan-Marek Glogowski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #3 from Jan-Marek Glogowski --- This reads a lot like bug 143206. Are you using some non-breeze theme, especially kvantum? See my current comment in that bug (bug 143206 comment 21 that is). Maybe it's not kavantum specific, but again some QtWayland bug... Please reset the bug to UNCONFIRMED after providing the info. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 143206, which changed state. Bug 143206 Summary: Libreoffice on plasma works really bad https://bugs.documentfoundation.org/show_bug.cgi?id=143206 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143206] Libreoffice on plasma works really bad
https://bugs.documentfoundation.org/show_bug.cgi?id=143206 Jan-Marek Glogowski changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|UNCONFIRMED |RESOLVED --- Comment #21 from Jan-Marek Glogowski --- This is definitely some upsteam bug. LO just gets single mouse click events. So I installed qt5-style-kvantum/stable for Debian Bullseye. For a double click I get 4 events AKA button down + up + down + up. SAL_DEBUG((int) eState << " " << aEvent.mnX << " " << aEvent.mnY << " " << aEvent.mnCode << " " << aEvent.mnTime); For breeze I get: debug:43565:43565: 0 278 201 1 13193371 debug:43565:43565: 1 278 201 0 13193418 debug:43565:43565: 0 278 201 1 13193515 debug:43565:43565: 1 278 201 0 13193578 For kvantum I get: debug:43277:43277: 0 288 206 1 0 debug:43277:43277: 1 288 206 0 13153386 debug:43277:43277: 0 288 206 1 13153485 debug:43277:43277: 1 288 206 0 13153571 The first timestamp is 0! That timestamp comes from Qt. And this also happens for a single click. I'm actually surprised anything happens ;-) I suggest to open a bug at https://github.com/tsujan/Kvantum Working around this bug looks messy and more like a heuristic, so I'll just close this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Bug 100156 depends on bug 143206, which changed state. Bug 143206 Summary: Libreoffice on plasma works really bad https://bugs.documentfoundation.org/show_bug.cgi?id=143206 What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144008] LO crashes when macro tries to start a form document in Base (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 --- Comment #6 from Commit Notification --- Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/76cb48b6a00cde41987a1b67b78fee68a133ad53 tdf#144008 Qt5/Kf5 create frames in the GUI thread It will be available in 7.2.2. 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] [Bug 144008] LO crashes when macro tries to start a form document in Base (kf5 only)
https://bugs.documentfoundation.org/show_bug.cgi?id=144008 Commit Notification changed: What|Removed |Added Whiteboard|target:7.3.0|target:7.3.0 target:7.2.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144116] Calc spreadsheet doesn't save text indent setting
https://bugs.documentfoundation.org/show_bug.cgi?id=144116 Martin changed: What|Removed |Added Version|7.2.0.3 rc |7.2.0.4 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144116] New: Calc spreadsheet doesn't save text indent setting
https://bugs.documentfoundation.org/show_bug.cgi?id=144116 Bug ID: 144116 Summary: Calc spreadsheet doesn't save text indent setting Product: LibreOffice Version: 7.2.0.3 rc Hardware: ARM OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mar...@martindavies.id.au Description: Setting an indent level for text in a cell reverts to 0pt after saving, closing and re-opening file. Steps to Reproduce: 1. In Calc select a cell or complete column. 2. Select Format>Cells... then change Text Alignment>Horizontal-Left>Indent-2pt. 3. Save and close sheet, then re-open. Indent reverts to 0pt. Actual Results: Cell indent reverts to 0pt. Expected Results: Cell indent is saved. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Mac OS X (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Bug 103341 depends on bug 116315, which changed state. Bug 116315 Summary: Cycle Case does not use Sentence case or tOGGLE cASE https://bugs.documentfoundation.org/show_bug.cgi?id=116315 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144037] kf5: Unable to insert table from toolbar button
https://bugs.documentfoundation.org/show_bug.cgi?id=144037 --- Comment #5 from Commit Notification --- Jan-Marek Glogowski committed a patch related to this issue. It has been pushed to "libreoffice-7-2": https://git.libreoffice.org/core/commit/7c1f4284562e905372b5c14b6017f1eb438f54b5 tdf#144037 Qt5 just close popup with mouse outside It will be available in 7.2.2. 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] [Bug 144037] kf5: Unable to insert table from toolbar button
https://bugs.documentfoundation.org/show_bug.cgi?id=144037 Commit Notification changed: What|Removed |Added Whiteboard|target:7.3.0|target:7.3.0 target:7.2.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142889] Unable to copy/paste images from native QT applications on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=142889 --- Comment #3 from Jan-Marek Glogowski --- Already got a reply. It's very likely a Qt bug fixed by https://codereview.qt-project.org/c/qt/qtwayland/+/366769 Workarounds for LO would still leave all other non-qt apps buggy with Plasma, so I think this needs to wait for fixed Qt5 :-( -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Bug 103341 depends on bug 116315, which changed state. Bug 116315 Summary: Cycle Case does not use Sentence case or tOGGLE cASE https://bugs.documentfoundation.org/show_bug.cgi?id=116315 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102495 Bug 102495 depends on bug 142889, which changed state. Bug 142889 Summary: Unable to copy/paste images from native QT applications on Wayland https://bugs.documentfoundation.org/show_bug.cgi?id=142889 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 100156] [META] Wayland-related bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=100156 Bug 100156 depends on bug 142889, which changed state. Bug 142889 Summary: Unable to copy/paste images from native QT applications on Wayland https://bugs.documentfoundation.org/show_bug.cgi?id=142889 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142889] Unable to copy/paste images from native QT applications on Wayland
https://bugs.documentfoundation.org/show_bug.cgi?id=142889 Jan-Marek Glogowski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTOURBUG --- Comment #2 from Jan-Marek Glogowski --- So Debian Bullseye is out, I just updated my Buster and now tried to repo some Wayland LO bugs. I used Spectacle and simply copied the screenshot into clipboard. $ wl-paste -l application/x-qt-image x-kde-force-image-copy image/png image/avif image/bmp ... [many more] On paste LO requests "image/png" (I didn't look into the code why; probably because it's the first image). $ wl-paste -t image/png >/tmp/unknown.data $ hexdump -C /tmp/unknown.data | head -n 1 42 4d 36 ec 5e 00 00 00 00 00 36 00 00 00 28 00 |BM6.^.6...(.| The clipboard delivers "image/bmp" instead :-( While it's a KDE desktop, also the gtk3 VCL can't paste that image, because LO tries to decode the clipboard data with the PNG reader and fails. KDE bug tracker already has: https://bugs.kde.org/show_bug.cgi?id=436956, so I'll report there first. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144115] New: libjava_gcc3.so: cannot open shared object file (missing lib or packaging error?)
https://bugs.documentfoundation.org/show_bug.cgi?id=144115 Bug ID: 144115 Summary: libjava_gcc3.so: cannot open shared object file (missing lib or packaging error?) Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com At startup with --writer option, these errors appear on the terminal: warn:sal.osl:44331:44331:sal/osl/unx/module.cxx:155: dlopen(/.../libreofficedev7.3/program/libjava_gcc3.so, 257): /home/admin/lotest/7.3.0.0.alpha0/opt/libreofficedev7.3/program/libjava_gcc3.so: cannot open shared object file: No such file or directory warn:sal.osl:44331:44331:sal/osl/unx/module.cxx:155: dlopen(/.../libreofficedev7.3/program/libgcc3_java.so, 257): /home/admin/lotest/7.3.0.0.alpha0/opt/libreofficedev7.3/program/libgcc3_java.so: cannot open shared object file: No such file or directory warn:unotools.config:44331:44331:unotools/source/config/configmgr.cxx:153: ConfigManager not empty This happens with --writer option but not if soffice is started without options. STEPS TO REPRODUCE: 1. /path/to/libreofficedev7.3/program/soffice --safe-mode --writer # Note --safe-mode is just to eliminate profile dependencies 2. When the "safe mode" dialog appears, click "Continue in Safe Mode" RESULTS: The above messages appears on the terminal. This is on 64-bit Ubuntu Linux. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 282b2d8bfd6fb16f58fb177910427b031dc80066 CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-26_09:43:29 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143894] 7.2.0.3 release: external skia build fails with freetype 2.11
https://bugs.documentfoundation.org/show_bug.cgi?id=143894 Adolfo Jayme changed: What|Removed |Added Whiteboard||target:7.3.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144114] New: Exception trying to find if xxx is encrypted: com.sun.star.ucb.InteractiveAugmentedIO
https://bugs.documentfoundation.org/show_bug.cgi?id=144114 Bug ID: 144114 Summary: Exception trying to find if xxx is encrypted: com.sun.star.ucb.InteractiveAugmentedIO Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com Created attachment 174566 --> https://bugs.documentfoundation.org/attachment.cgi?id=174566=edit typescript When starting up normally with no arguments, i.e. using your existing profile, many messages appear on the terminal about previously-edited files (which may or may not still exist), like these: warn:sfx:42797:42797:sfx2/source/control/recentdocsview.cxx:90: caught exception trying to find out if doc is encrypted: com.sun.star.ucb.InteractiveAugmentedIOException message: an error occurred during file opening Code: 22 I will attach a typescript file showing what I see. All the messages seem to be related to spreadsheets; they appear if "soffice" is run without arguments, or with --calc, but NOT if invoked with e.g. --writer. STEPS TO REPRODUCE: 1. Create or edit some spreadsheets (if necessary) to establish a profile with history of such files. 2. /path/to/libreofficedev7.3/program/soffice RESULTS: Many "caught exception" messages, as shown in the attached typescript. EXPECTED RESULTS: Nothing written to terminal unless the user should do something. Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 282b2d8bfd6fb16f58fb177910427b031dc80066 CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-26_09:43:29 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144113] New: "Optimizing could fail with beziers!"
https://bugs.documentfoundation.org/show_bug.cgi?id=144113 Bug ID: 144113 Summary: "Optimizing could fail with beziers!" Product: LibreOffice Version: 7.3.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com At startup, libreoffice always emits warnings like this: warn:legacy.tools:42390:42390:tools/source/generic/poly.cxx:1033: Optimizing could fail with beziers! (repeated 7 times) STEPS TO REPRODUCE: 1. /path/to/libreofficedev7.3/program/soffice --safe-mode RESULTS: Warnings on the terminal EXPECTED RESULTS: Clean terminal (nothing output unless user intervention is needed) Version: 7.3.0.0.alpha0+ / LibreOffice Community Build ID: 282b2d8bfd6fb16f58fb177910427b031dc80066 CPU threads: 12; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2021-08-26_09:43:29 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144112] New: problem for a .xlsx file with password
https://bugs.documentfoundation.org/show_bug.cgi?id=144112 Bug ID: 144112 Summary: problem for a .xlsx file with password Product: LibreOffice Version: 7.0.0.3 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: michel.pambouk...@orange.fr Description: password seems to be accepted but the file is not opened Steps to Reproduce: 1.first create a .xlsx file with password using microsoft 2.then try to open it with libreoffice 3. Actual Results: password accepted file not openned Expected Results: open the file Reproducible: Always User Profile Reset: No Additional Info: nothing happens -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143482] Make it easier to open Master Document subdocuments
https://bugs.documentfoundation.org/show_bug.cgi?id=143482 --- Comment #7 from L Duperval --- Here it is: https://www.loom.com/share/018151f1df4d4f368a733ac7f0174f23 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143730] Spell Checker giving wrong spelling
https://bugs.documentfoundation.org/show_bug.cgi?id=143730 Aleksandra changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from Aleksandra --- Hello John McGill! Please add version information. This will help us figure it out faster. Thank you in advance! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143730] Spell Checker giving wrong spelling
https://bugs.documentfoundation.org/show_bug.cgi?id=143730 --- Comment #1 from Aleksandra --- The bug is not reproduced in Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143764] bump scroll too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=143764 --- Comment #2 from Aleksandra --- The bug is not reproduced in Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143764] bump scroll too fast
https://bugs.documentfoundation.org/show_bug.cgi?id=143764 Aleksandra changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Aleksandra --- Hello j...@jmbaai.com, may I ask you to record a video reproducing your bug? Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144111] LO72 on macOS: copy/paste not working properly
https://bugs.documentfoundation.org/show_bug.cgi?id=144111 Martin Srebotnjak changed: What|Removed |Added Severity|normal |major Priority|medium |high --- Comment #1 from Martin Srebotnjak --- Sorry, setting to high+major, as copy/paste are really most basic office suite document editing functions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144111] New: LO72 on macOS: copy/paste not working properly
https://bugs.documentfoundation.org/show_bug.cgi?id=144111 Bug ID: 144111 Summary: LO72 on macOS: copy/paste not working properly Product: LibreOffice Version: 7.2.0.4 release Hardware: All OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mi...@filmsi.net Description: Copying and pasting on macOS with LO72* is not working. You get to paste some previous system clipboard content, not the one you selected and copied. Steps to Reproduce: 1. Open LO Writer with an ODT document. 2. Select some text and copy it (using either cmd+c or menu command). 3. Paste (using either cmd+p or menu command). Actual Results: You paste not the copied text from step 2, but some previously copied clipboard content. Expected Results: You should paste content from step 2. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.1.0+ / LibreOffice Community Build ID: ac3207d3b2c3b6580de14132fd12e9c6fedc6502 CPU threads: 8; OS: Mac OS X 10.16; UI render: default; VCL: osx Locale: sl-SI (sl_SI.UTF-8); UI: sl-SI Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 67013] FILESAVE: border of header disappears when saving in anything but .odt /.ott
https://bugs.documentfoundation.org/show_bug.cgi?id=67013 Timur changed: What|Removed |Added Resolution|NOTABUG |NOTOURBUG --- Comment #17 from Timur --- NotABug is when something works, just needed an explanation. This would be NotOurBug then. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Bug 103341 depends on bug 116315, which changed state. Bug 116315 Summary: Cycle Case does not use Sentence case or tOGGLE cASE https://bugs.documentfoundation.org/show_bug.cgi?id=116315 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144106] FILEOPEN: LibreOffice crashes on opening CSV file
https://bugs.documentfoundation.org/show_bug.cgi?id=144106 --- Comment #6 from Uwe Auer --- No repro Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 4debb7e8cc12563f46d1aaa58afdcb831f21cc83 CPU threads: 1; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144070] Filesave DOCX / DOC / ODT: Abnormal increase in size because no-DPI JPEG image saved as large PNG
https://bugs.documentfoundation.org/show_bug.cgi?id=144070 Timur changed: What|Removed |Added Summary|Filesave DOCX / DOC / ODT: |Filesave DOCX / DOC / ODT: |Abnormal increase in size |Abnormal increase in size |because JPEG image saved as |because no-DPI JPEG image |large PNG |saved as large PNG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144106] FILEOPEN: LibreOffice crashes on opening CSV file
https://bugs.documentfoundation.org/show_bug.cgi?id=144106 --- Comment #5 from Uwe Auer --- No repro Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded No repro Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded No repro Version: 7.2.0.4 (x64) / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 1; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-US (en_DE); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103341] [META] AutoCorrect and Word Completion bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103341 Bug 103341 depends on bug 116315, which changed state. Bug 116315 Summary: Cycle Case does not use Sentence case or tOGGLE cASE https://bugs.documentfoundation.org/show_bug.cgi?id=116315 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126624] Suggested database connection string parameters incorrect in URL entry dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=126624 --- Comment #14 from Alex Thurgood --- Bug is still present in LO7152, 7204 and LODev73alpha. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42989] FORMATTING: Selecting Multiple Cells with Different Formats Show as Same Format and Can't Be Changed as a Group
https://bugs.documentfoundation.org/show_bug.cgi?id=42989 --- Comment #17 from weddingvedas --- awesome and usefull article. https://weddingvedas.com/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144101] LibreOfficeDev - Immediate crash when attempting to edit a database report
https://bugs.documentfoundation.org/show_bug.cgi?id=144101 --- Comment #4 from Alex Thurgood --- Is this really a duplicate of bug 117159? The backtraces are different and the described behaviour leading to the crash is different. In this report, simply opening the report in Edit mode causes the crash, whereas in bug 117159 the crash is caused when attempting to edit a chart object. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119495] New case "Sentence case" during cycling Shift+F3 is applied to whole sentence
https://bugs.documentfoundation.org/show_bug.cgi?id=119495 V Stuart Foote changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |6315| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144033] Libreoffice (Calc) rendering very slow on GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=144033 --- Comment #10 from saverio.p...@gmail.com --- Note that just today I've swapped the GPU with a more powerful one, which I think explains why the CPU occupation is not reaching 100%+; 85/90% is still very high though, and makes lag still very noticeable. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144033] Libreoffice (Calc) rendering very slow on GTK3
https://bugs.documentfoundation.org/show_bug.cgi?id=144033 --- Comment #9 from saverio.p...@gmail.com --- Results of keeping key `s` pressed in a Calc sheet, in a file of mine (not particularly large, around 350 rows in total): - 7.2.0.4 official (gtk3): 85/90% - 7.1.5rc2 ppa:libreoffice/ppa (no theme): 5/10% - 7.1.5rc2 ppa:libreoffice/ppa (gtk3): 85/90% The value on the right is the CPU occupation while the key is pressed. The source reported as official is the www.libreoffice.org, installed via DEB packages. In order to test the official distribution, I've removed (not purged; I think it doesn't make any difference) all the packages matching `libobasis` and `libreoffice`, then installed the DEB packages. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144106] FILEOPEN: LibreOffice crashes on opening CSV file
https://bugs.documentfoundation.org/show_bug.cgi?id=144106 Julien Nabet changed: What|Removed |Added Ever confirmed|1 |0 CC|serval2...@yahoo.fr | Status|NEEDINFO|UNCONFIRMED --- Comment #4 from Julien Nabet --- Ok thank you for your feedback. I don't have more questions so put back to UNCONFIRMED and uncc myself. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144110] How do I eliminate the Track Changes toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=144110 JIM7 changed: What|Removed |Added Hardware|All |x86-64 (AMD64) OS|All |Windows (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144110] New: How do I eliminate the Track Changes toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=144110 Bug ID: 144110 Summary: How do I eliminate the Track Changes toolbar Product: LibreOffice Version: 7.1.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: j...@fastmail.us I use the track changes while editing, but I *NEVER* use the "Track Changes" toolbar. All that toolbar does, is get in my way. I HATE IT! Can it safely be removed from my 7.1.4.2 version of LibreOffice Writer? Thank you. > I use a component made PC with WIN-7. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142415] Using mouse click in a base to launch a macro from a cell in a table control does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=142415 Buovjaga changed: What|Removed |Added Version|7.1.3.2 release |7.1.0.0.alpha0+ CC||caol...@redhat.com Keywords|bibisectRequest |bibisected, bisected --- Comment #7 from Buovjaga --- (In reply to Robert Großkopf from comment #6) > (In reply to Buovjaga from comment #5) > > (In reply to Robert Großkopf from comment #4) > > Please, can you explain how I can see the problem in attachment 113999 > > [details] > > [details]? If I edit the form and control properties of the control in > > Tablecontrol, the events are empty even in 7.0 and 6.3. > > Have a look at form Kontakte_Query_not_editable_Tablecontrol. > Open the form for editing. > Right Mousbutton on "Name" → Column → Events: Mous button released is linked > to Main > Right Mousbutton on "EMail" → Column → Events: Mous button pressed is linked > to Main > Right Mousbutton on "Web" → Column → Events: When receiving focus is linked > to Main > It is nearly the same in the form Kontakte_Query_editable_Tablecontrol. Only > "Web" is linked by "Mouse inside". > > Every field is linked to the same macro which only shows a msgbox "Event > happens". > Please click with mouse on the tablecontrol of > Kontakte_Query_editable_Tablecontrol. The msgbox will appear. Might be you > have to click not only one time for it. on LO t.o.* and earlier versions. Thanks, I was actually looking at the wrong attachment, but your explanation was still crucial :) I double-clicked Kontakte_Query_editable_Tablecontrol to open it and then clicked on the data entries a few times to try and provoke the event. Bibisected with linux-64-7.1 to https://git.libreoffice.org/core/commit/a751d9c414fc63f36ae4b54b8adbaba042b31f60 weld FormattedControl Adding Cc: to Caolán McNamara -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144109] New: In LO Calc, the UI Side Bar is very jerky and flickers when scrolling the Properties menu when all the properties are expanded.
https://bugs.documentfoundation.org/show_bug.cgi?id=144109 Bug ID: 144109 Summary: In LO Calc, the UI Side Bar is very jerky and flickers when scrolling the Properties menu when all the properties are expanded. Product: LibreOffice Version: 7.2.0.2 rc Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tarotf...@protonmail.com Description: In LO Calc, the Side Bar is very jerky and flickers when scrolling the Properties menu when all the properties are expanded (apparently the default setting, which is appropriate because that's most useful). This does NOT happen in LO Writer. This is a serious issue because this flickering can trigger an epileptic seizure. Steps to Reproduce: 1. Open Calc document 2. Open Properties in the Side Bar 3. Scroll through list with all properties opened (worst when using the scroll grab bar to scroll) Actual Results: Very jerky or flickering of the properties menu when it's being scrolled. Expected Results: Smooth scrolling. Reproducible: Always User Profile Reset: Yes Additional Info: Version: 7.2.0.2 (x64) / LibreOffice Community Build ID: 614be4f5c67816389257027dc5e56c801a547089 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142415] Using mouse click in a base to launch a macro from a cell in a table control does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=142415 --- Comment #6 from Robert Großkopf --- (In reply to Buovjaga from comment #5) > (In reply to Robert Großkopf from comment #4) > > First I thought this might be a duplicate of bug 89917. Then I tested with > > https://bugs.documentfoundation.org/attachment.cgi?id=113999 and detected: > > Not only the events of write protected tablecontrol has been gone. The > > events from mouse in editable tablecontrols has also been gone. > > > > This works in LO 7.0.5.2, fails with LO 7.1.3.2 on OpenSUSE 15.2 64bit rpm > > Linux. > > Please, can you explain how I can see the problem in attachment 113999 > [details]? If I edit the form and control properties of the control in > Tablecontrol, the events are empty even in 7.0 and 6.3. Have a look at form Kontakte_Query_not_editable_Tablecontrol. Open the form for editing. Right Mousbutton on "Name" → Column → Events: Mous button released is linked to Main Right Mousbutton on "EMail" → Column → Events: Mous button pressed is linked to Main Right Mousbutton on "Web" → Column → Events: When receiving focus is linked to Main It is nearly the same in the form Kontakte_Query_editable_Tablecontrol. Only "Web" is linked by "Mouse inside". Every field is linked to the same macro which only shows a msgbox "Event happens". Please click with mouse on the tablecontrol of Kontakte_Query_editable_Tablecontrol. The msgbox will appear. Might be you have to click not only one time for it. on LO t.o.* and earlier versions. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138877] Should LibreOffice be giving a warning when a document is opened, but the template from which it was created is deleted?
https://bugs.documentfoundation.org/show_bug.cgi?id=138877 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #4 from BogdanB --- Also tested in Version: 5.4.7.2 Build ID: c838ef25c16710f8838b1faec480ebba495259d0 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk2; Locale: ro-RO (ro_RO.UTF-8); Calc: group No message there when templete for that file is no more there. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144106] FILEOPEN: LibreOffice crashes on opening CSV file
https://bugs.documentfoundation.org/show_bug.cgi?id=144106 --- Comment #3 from rob...@prino.org --- It works abso-fluck-ingly flawlessly with 7.1.5.2, to which I had to revert, by uninstalling 7.2, which wiped out I don't know how many settings - suddenly the Spanish dictionary came back as did South-African English as a interface language... Needlessly to say, I will stay on 7.1.5.2, as this situation should never ever have passed any QA. And as for "Corrupted user profile", if you don't know what causes it, *I* am not going to reset anything! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 120853] [META] DOC (binary) document protection-related issues/enhancement
https://bugs.documentfoundation.org/show_bug.cgi?id=120853 Justin L changed: What|Removed |Added Depends on||89385 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=89385 [Bug 89385] Edit mode is password is not working on DOC files -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89385] Edit mode is password is not working on DOC files
https://bugs.documentfoundation.org/show_bug.cgi?id=89385 Justin L changed: What|Removed |Added Blocks||120853 --- Comment #9 from Justin L --- confirmed: opening password is requested. Editing is possible by going to Format - Sections - and removing the protected status from the section (no password is requested). I didn't see a duplicate in the META bug, but I expect I've seen this before... Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=120853 [Bug 120853] [META] DOC (binary) document protection-related issues/enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 93210] disappearing line in LibO after click
https://bugs.documentfoundation.org/show_bug.cgi?id=93210 --- Comment #9 from Justin L --- I don't understand the point of this bug report at all. So, the document has too much text to actually be shown in a single cell. And clicking in there make some of the text visible/invisible? Who cares? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104522] [META] DOCX (OOXML) header & footer-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104522 Bug 104522 depends on bug 67013, which changed state. Bug 67013 Summary: FILESAVE: border of header disappears when saving in anything but .odt /.ott https://bugs.documentfoundation.org/show_bug.cgi?id=67013 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 67013] FILESAVE: border of header disappears when saving in anything but .odt /.ott
https://bugs.documentfoundation.org/show_bug.cgi?id=67013 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #16 from Justin L --- (In reply to Luke Deller from comment #9) > Microsoft Word does not actually support the concept of setting a border on > a header/footer. Thus NOTABUG > If instead you set the border on the paragraph within the header, rather > than on the header itself, then this comes through fine into doc or docx This kind of emulation is not worth all the pitfalls it will cause. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144108] New: Calc application color changes inconsistent.
https://bugs.documentfoundation.org/show_bug.cgi?id=144108 Bug ID: 144108 Summary: Calc application color changes inconsistent. Product: LibreOffice Version: 7.1.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ruven.gottl...@gmail.com When changing background color in calc doc to black, color for all lines is inverted to white. However, the highlighted cell borders stay black, rendering the cell invisible. When changing background color in calc doc to e.g. dark blue, color for all lines is inverted to white. However, cell contents, and the highlighted cell borders stay black. The cell border lines, cell contents, and highlighted cell border color ought to be changed in a consistent manner. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144106] FILEOPEN: LibreOffice crashes on opening CSV file
https://bugs.documentfoundation.org/show_bug.cgi?id=144106 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Julien Nabet --- On pc Debian x86-64 with master sources updated today or with LO Debian package 7.4.5, I don't reproduce this. Could you test with LO 7.1.5 or brand 7.2.0 ? Also, can you give a try at https://wiki.documentfoundation.org/QA/FirstSteps ? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 138990] ODBC - LO, LO Vanilla, Collabora Office fail to retrieve ODBC datasources on M1 Apple Silicon
https://bugs.documentfoundation.org/show_bug.cgi?id=138990 Julien Nabet changed: What|Removed |Added CC||serval2...@yahoo.fr --- Comment #3 from Julien Nabet --- Alex: searching about your error message, I saw this: https://blog.devart.com/iodbc-driver-manager-for-apple-silicon-m1.html "...ODBC drivers for Mac require the iODBC driver manager, but it appears that the current version only supports the x64-86 Intel architecture. After seeing numerous complaints about using ODBC drivers from users of the new Macs, we decided to build iODBC for the x64-86 and arm64 architectures from the source code of v.3.52.14 and share it with the ODBC community...". Does it correspond to what you installed? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132616] FILESAVE: ODT->DOC/X: deleted track-changes content not completely marked as deleted
https://bugs.documentfoundation.org/show_bug.cgi?id=132616 Justin L changed: What|Removed |Added Keywords||filter:docx Summary|FILESAVE: DOC: Page break |FILESAVE: ODT->DOC/X: |added after every heading |deleted track-changes ||content not completely ||marked as deleted --- Comment #4 from Justin L --- This ODT actually is 30 pages of deleted content - visible when you View - Show tracked changes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 65152] CALC: Superscript and Spacing character formats not copied by Clone Formatting - clarify Help per Comment 7
https://bugs.documentfoundation.org/show_bug.cgi?id=65152 Rafael Lima changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |rafael.palma.l...@gmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142415] Using mouse click in a base to launch a macro from a cell in a table control does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=142415 Buovjaga changed: What|Removed |Added CC||ilmari.lauhakangas@libreoff ||ice.org --- Comment #5 from Buovjaga --- (In reply to Robert Großkopf from comment #4) > First I thought this might be a duplicate of bug 89917. Then I tested with > https://bugs.documentfoundation.org/attachment.cgi?id=113999 and detected: > Not only the events of write protected tablecontrol has been gone. The > events from mouse in editable tablecontrols has also been gone. > > This works in LO 7.5.0.2, fails with LO 7.1.3.2 on OpenSUSE 15.2 64bit rpm > Linux. Please, can you explain how I can see the problem in attachment 113999? If I edit the form and control properties of the control in Tablecontrol, the events are empty even in 7.0 and 6.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144107] Editing: page breaks is not visible without gridlines
https://bugs.documentfoundation.org/show_bug.cgi?id=144107 --- Comment #2 from Uwe Auer --- No repro in Version: 7.1.5.2 / LibreOffice Community Build ID: 85f04e9f809797b8199d13c421bd8a2b025d52b5 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144107] Editing: page breaks is not visible without gridlines
https://bugs.documentfoundation.org/show_bug.cgi?id=144107 --- Comment #1 from Uwe Auer --- Repro Version: 7.2.0.4 / LibreOffice Community Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
