[Libreoffice-bugs] [Bug 149587] Using the CMD shortcuts for styles causes app to crash.
https://bugs.documentfoundation.org/show_bug.cgi?id=149587 --- Comment #3 from Alex Thurgood --- If the Cmd+key combo caused a context switch and forced redraw of the LO UI, then this would belong to the same group of scheduling issues that have since been fixed. @Robert: please try with a current 7.5 pre-release or a daily dev release. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147020] Default Printer not recognized
https://bugs.documentfoundation.org/show_bug.cgi?id=147020 Alex Thurgood changed: What|Removed |Added Whiteboard| QA:needsComment| --- Comment #3 from Alex Thurgood --- @Steve: the comment under whiteboard was intended for actiln by a member of the QA team, but as the problem has subsequently been resolved, per your comment 2, we can mark this as resolved wfm. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147020] Default Printer not recognized
https://bugs.documentfoundation.org/show_bug.cgi?id=147020 Alex Thurgood changed: What|Removed |Added Resolution|--- |WORKSFORME Status|UNCONFIRMED |RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152515] PrintOut Unlike the display, some characters are rotated.(Windows Only)
https://bugs.documentfoundation.org/show_bug.cgi?id=152515 --- Comment #22 from Saburo --- Created attachment 184334 --> https://bugs.documentfoundation.org/attachment.cgi?id=184334=edit Font(VL Gothic) Microsoft Print to PDF VL Gothic(2022-06-12) rotate "（" U+FF08 , "）" U+FF09 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152662] services
https://bugs.documentfoundation.org/show_bug.cgi?id=152662 himajin100...@gmail.com changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152662] services
https://bugs.documentfoundation.org/show_bug.cgi?id=152662 himajin100...@gmail.com changed: What|Removed |Added Component|LibreOffice |deletionRequest Status|REOPENED|RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152662] services
https://bugs.documentfoundation.org/show_bug.cgi?id=152662 himajin100...@gmail.com changed: What|Removed |Added Ever confirmed|0 |1 Status|CLOSED |REOPENED Resolution|INVALID |--- -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152662] services
https://bugs.documentfoundation.org/show_bug.cgi?id=152662 himajin100...@gmail.com changed: What|Removed |Added Status|RESOLVED|CLOSED Version|3.3.0 release |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152662] services
https://bugs.documentfoundation.org/show_bug.cgi?id=152662 himajin100...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Component|Base|LibreOffice Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143987] Stylist: Merge PS and CS into one Text Styles view
https://bugs.documentfoundation.org/show_bug.cgi?id=143987 --- Comment #14 from Mike Kaganski --- (In reply to David from comment #13) Hmm, I'm sorry how comments 11-13 relate to the problem discussed here, and wonder why have they appeared here: I presume, they intend to help decide on something? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152441] An option to add to writing aids
https://bugs.documentfoundation.org/show_bug.cgi?id=152441 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 152440] Switching between page views switches to semi-random pages
https://bugs.documentfoundation.org/show_bug.cgi?id=152440 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 150582] Words with smart quotes/apostrophes get added to custom dictionaries via Writer but not Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=150582 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 152444] Please add ability to add hyperlinks to page numbers for an alphabetical index.
https://bugs.documentfoundation.org/show_bug.cgi?id=152444 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 152437] Align & Distribute multiple inserted images within a Writer document
https://bugs.documentfoundation.org/show_bug.cgi?id=152437 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 152438] Improvement needed in LibreOffice submenu
https://bugs.documentfoundation.org/show_bug.cgi?id=152438 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 149735] MP4 video does not play correctly when showing a presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=149735 --- Comment #3 from QA Administrators --- Dear Aleksandr, 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 149193] Freezes when selecting font on Ubuntu 22.04
https://bugs.documentfoundation.org/show_bug.cgi?id=149193 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 149193] Freezes when selecting font on Ubuntu 22.04
https://bugs.documentfoundation.org/show_bug.cgi?id=149193 --- Comment #3 from QA Administrators --- Dear Robert Wilson, 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 149731] Crash Report 5c0ae914-0d0e-42b1-bee0-2b611fff0b00
https://bugs.documentfoundation.org/show_bug.cgi?id=149731 --- Comment #2 from QA Administrators --- Dear Jim Robinson, 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 90739] FORMULA EXPORTING: exporting formula to MS word loses formatting, shifts rendered image
https://bugs.documentfoundation.org/show_bug.cgi?id=90739 --- Comment #32 from QA Administrators --- Dear Yury, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147171] EDITING: Page breaks revert to portrait although set to landscape
https://bugs.documentfoundation.org/show_bug.cgi?id=147171 --- Comment #2 from QA Administrators --- Dear emery.peter, 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 59181] docx formulas with messed parentheses hierarchy don't show correctly in LibO
https://bugs.documentfoundation.org/show_bug.cgi?id=59181 --- Comment #15 from QA Administrators --- Dear Ruslan Kabatsayev, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139110] FILEOPEN RTF: Text frame in autoshape textbox is mispositioned
https://bugs.documentfoundation.org/show_bug.cgi?id=139110 --- Comment #7 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137717] QR Code Generation in a new blank calc sheet doesn't force sheet save on exit
https://bugs.documentfoundation.org/show_bug.cgi?id=137717 --- Comment #4 from QA Administrators --- Dear Colin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137548] FILEOPEN Table in compat14 DOCX/DOC should split full row, not move to next page (compat15 is OK)
https://bugs.documentfoundation.org/show_bug.cgi?id=137548 --- Comment #7 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105346] Swash glyph clipped (EB Garamond)
https://bugs.documentfoundation.org/show_bug.cgi?id=105346 --- Comment #8 from QA Administrators --- Dear Volga, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151664] Rendered text shifted with some Hebrew fonts - but not in PDF output
https://bugs.documentfoundation.org/show_bug.cgi?id=151664 --- Comment #17 from u...@net9.ga --- As of Version: 7.4.3.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 2; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 7.4.3-3 Calc: threaded I do see the bug with attachment 183167. Which, for me, is using the (plain) Noto Sans fonts. But when I switch the problematic paragraphs to Noto Sans Arabic, or to Noto Sans Hebrew, as appropriate, the bug disappears. I also seem to be able to switch the bug on, and off, by changing the fonts between the language specific Noto Sans variant, and the plain, non language specific, Noto Sans fonts. Does that mean that with multi languages documents, the user will have to constantly change the fonts? For me, searching for a specific fonts in the drop down fonts menu was tedious. Is it because I do not know the short way to search that menu? As an aside, there does not seem to be English Noto Sans. Nor Latin Noto Sans. Is what I called plain Noto Sans actually Latin Noto Sans? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 125600] Calc spellcheck does not recognize correct spelling of KWh
https://bugs.documentfoundation.org/show_bug.cgi?id=125600 --- Comment #5 from Richard Urwin --- Tested on 7.3.7.2 (x64) Windows 10 build The behaviour seems to have changed. kWh is now an accepted word. There is no red underline and it is not reported in a manual spellcheck However, MWh (megawatt hours) still triggers the two-capital auto-correct. Having disabled that, it is marked as an incorrect spelling with the recommended correction being MW h, with a space. It is difficult to imagine how this could be fixed without implementing an entire units parser. MWh is an unusual unit, whereas kWh is very common since it is the unit used to charge consumers for electricity. It makes sense if kWh is in the dictionary but not MWh. As a side issue, Calc accepts both Kph and Mph, which I would argue is incorrect; the units are kph and mph. An initial capital will result from auto-capitalization of the beginning of a sentence. This may introduce a typo into the document. Whether this is desired may depend on genre and context. A cell called "mph per second" should not be capitalized. Whereas if it is an English sentence outside strict science writing, such as "Mph is a unit of speed" then capitalization might look more natural. In summary, it's a complex problem where a full solution would involve a lot of code and some user-visible options. This isn't the right place to discuss that. If the commonly used units are included, and this one is, then I would suggest that the bug is marked as fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152477] Upon opening Calc the user is presented with a dialog box stating that calc had crashed the previous time when it hadn't
https://bugs.documentfoundation.org/show_bug.cgi?id=152477 --- Comment #27 from Howard Feldman --- No problem about the delay. You have just mirrored everything that I experienced. Since I am running with a Fedora base and you are using a Debian base it seems to be distribution agnostic. I will be upgrading my system to Fedora 37 sometime this weekend and that will probably update my desktop Cinnamon version. I will try LO again and if anything significant happens I'll report the results. I made a virtualbox stripped down version of my existing Fedora / Cinnamon setup and can reliably reproduce the bug so I can troubleshoot this with anyone who needs to. Alternatively, I can upload the virtual machine to anyone's site who wants it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152477] Upon opening Calc the user is presented with a dialog box stating that calc had crashed the previous time when it hadn't
https://bugs.documentfoundation.org/show_bug.cgi?id=152477 --- Comment #26 from Carl --- Sorry about the delay. Holidays... Anyway, I am still on my Linux Mint 20.1 Mate edition machine, LO 7.4.2.3, and can now reliably reproduce the bug. If I open a spreadsheet, or csv file in Calc, and copy something, it doesn't matter if I paste it anywhere, the next time I open a spreadsheet I get the crash message. While a document is still open, if I open others I don't get the message. If I don't copy, but close all documents, then next time I open one, I don't get the message. If I open one, do nothing but highlight one cell and Ctrl-C, then close the document, the next time I open any LO document, I get the crash message. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145599] Calc Charts display gets corrupted when you draw a line inside them
https://bugs.documentfoundation.org/show_bug.cgi?id=145599 --- Comment #11 from nobu --- https://bugs.documentfoundation.org/show_bug.cgi?id=152077 Similarly, it should be available in the next version 7.4.? . -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151525] FILEOPEN: LibreOffice Draw renders emojis from some PDFs as the Unicode Replacement Character '�'
https://bugs.documentfoundation.org/show_bug.cgi?id=151525 --- Comment #12 from خالد حسني --- This sounds like an encoding issue, possibly the PDF importer is mishandling surrogate pairs and they end up converted to replacement character which is often used in encoding errors. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143987] Stylist: Merge PS and CS into one Text Styles view
https://bugs.documentfoundation.org/show_bug.cgi?id=143987 --- Comment #13 from David --- (In reply to Mike Kaganski from comment #12) > (In reply to David from comment #11) > > That's what makes the Styles Formatting Toolbar such a powerful resource for > > accessing core styles. > > What's what makes the Styles Formatting Toolbar such a powerful resource? > Your phrase is completely cryptic, making me wonder what does it mean, and > not explaining anything. The ability to have a set of core styles on its own toolbar provides a very convenient way to have another place in which to select frequently used styles. I ditched the standard toolbar and don't miss it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152661] "Hybrid PDF" must share embedded media between the ODT and the proper PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=152661 --- Comment #2 from Eyal Rozenberg --- (In reply to V Stuart Foote from comment #1) > Why? > > Not sure there is any means to do this--PDF and ODF are radically different > document formats. Of course there is - don't just concatenate the ODF. Entwine aspects of it with the PDF. Then, if you want a proper ODF document, you can extract it from the hybrid format. > That PDF can "hold" a fully described ODF document in a > LibreOffice "Hybrid PDF" is a nice means to deliver an editable PDF > rendering of an ODF source document. It's not "nice" - it doubles the size. > The cost is duplicated content and increased size--the PDF is fully rendered > by PDF viewer, and LibreOFfice can parse out the ODF stream for the source > document. You can have a fully renderable PDF, and data which can be reconstituted into an ODF. > Otherwise don't use it. This workflow will be improved if it doesn't double the size. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152661] "Hybrid PDF" must share embedded media between the ODT and the proper PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=152661 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org --- Comment #1 from V Stuart Foote --- Why? Not sure there is any means to do this--PDF and ODF are radically different document formats. That PDF can "hold" a fully described ODF document in a LibreOffice "Hybrid PDF" is a nice means to deliver an editable PDF rendering of an ODF source document. The cost is duplicated content and increased size--the PDF is fully rendered by PDF viewer, and LibreOFfice can parse out the ODF stream for the source document. If that is a work flow a user needs, great! It is functional. Accept the cost (PDF size) and get on with it. Otherwise don't use it. Not a lot of reason to refactor or make any attempt at reducing projects Hybrid PDF size. IHMO => INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152653] Introduce proper Paragraph Style support in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152653 Eyal Rozenberg changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from Eyal Rozenberg --- (In reply to m.a.riosv from comment #3) > Please take a look into: > https://wiki.documentfoundation.org/QA/BugReport That is a document about reporting bugs. I'm not reporting a bug, so that doesn't apply. Stop playing with the bug status please. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152653] Introduce proper Paragraph Style support in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152653 m.a.riosv changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 --- Comment #3 from m.a.riosv --- Please take a look into: https://wiki.documentfoundation.org/QA/BugReport specially 3.6 Status https://wiki.documentfoundation.org/QA/BugReport#Status -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143987] Stylist: Merge PS and CS into one Text Styles view
https://bugs.documentfoundation.org/show_bug.cgi?id=143987 --- Comment #12 from Mike Kaganski --- (In reply to David from comment #11) > That's what makes the Styles Formatting Toolbar such a powerful resource for > accessing core styles. What's what makes the Styles Formatting Toolbar such a powerful resource? Your phrase is completely cryptic, making me wonder what does it mean, and not explaining anything. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143987] Stylist: Merge PS and CS into one Text Styles view
https://bugs.documentfoundation.org/show_bug.cgi?id=143987 --- Comment #11 from David --- (In reply to Mike Kaganski from comment #10) > Indeed. Note however, that this would be less than the original idea here - > to have two style categories open at once. That's what makes the Styles Formatting Toolbar such a powerful resource for accessing core styles. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152645] LibreOffice interface improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=152645 --- Comment #13 from Michael FA --- (In reply to V Stuart Foote from comment #12) > this is issue of bug 37134, doing an MDI "multi-document interface" > > otherwise nothing new or substantive in the mock-ups > > IHMO => DUPLICATE Well yes friend, but my concepts are better designed and are in the LibreOffice interface itself, not in other programs. mine is easier to understand. You shouldn't just dismiss it out of the blue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150582] Words with smart quotes/apostrophes get added to custom dictionaries via Writer but not Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=150582 --- Comment #1 from Tammy --- I was able to reproduce the issue in: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 780d55199e54fafc3784691d5cf716c1bb92b0aa CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151704] FILEOPEN DOC/X Incorrect table cell height when width is very thin
https://bugs.documentfoundation.org/show_bug.cgi?id=151704 --- Comment #3 from Justin L --- Created attachment 184333 --> https://bugs.documentfoundation.org/attachment.cgi?id=184333=edit form261minimalEXAGERATED.docx: without gridafter, just thin last column This shows it wasn't really a regression. It is the same file as the original, but with less rows (to make debugging easier) and thus is a round-trip from LO. Now it doesn't have a grid-after anymore (since fake cells took their place). It still runs up against the same code that forces a 12pt height. Interestingly, the comment about using 12pt font already existed before the code that sets the height to 240. commit 6c3ae34e32539f8493a940666dbe16b23a8ba7b0 Author: Frank Meies on Tue Nov 20 15:24:54 2001 + Chg: Vertical Formatting - Growing frames -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152550] Drop the "Basic Fonts" option dialogs
https://bugs.documentfoundation.org/show_bug.cgi?id=152550 --- Comment #20 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #6) > Templates are for people who really need highly customized defaults. For > most, trying to enforce dealing with templates and styles would be really > unneeded and excessive complexity. So, this is my mentioned detriment (2.) . I said "some may argue", because, well, I've always been wary of setting any defaults in LO Settings. It's a scary place where it's difficult to figure out what effect your actions will have. Also, I'm not sure inexperienced users would even explore the LO settings hierarchy. Still, I recognize that adopting my suggestion would also necessitate doing some serious UI work to make it easier and accessible for inexperienced users to make changes to the "root defaults", i.e. in my suggestion to the default template. One way to achieve this would be having the style dialogs include some button or more complex UI which actually does this for you, which you would notice as you are surveing a Style's features. I think MS Word has something like that: http://www.addbalance.com/usersguide/images/2010StylesOrganizer.png And the link takes you to a "Style Organizer" for copying styles to the default template. https://www.avantixlearning.ca/wp-content/uploads/2015/09/StylesOrganizer.png -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148640] LibreOffice Draw hangs when changing Property pane size
https://bugs.documentfoundation.org/show_bug.cgi?id=148640 --- Comment #4 from Tammy --- I was unable to reproduce this issue in the following versions: Version: 7.4.2.3 (x64) / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 780d55199e54fafc3784691d5cf716c1bb92b0aa CPU threads: 8; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -Verified by opening the drawing and the right part of the window shows the properties pane. -Verified by changing the horizontal size of the property pane by drag of the left edge of the property pane and no flickering appears in either of the three tabs as well. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142468] LibreOffice randomly hangs on macOS Big Sur 2020 MacBook Air M1
https://bugs.documentfoundation.org/show_bug.cgi?id=142468 --- Comment #19 from Patrick Luby --- (In reply to M-Rick from comment #16) > I do have the same behaviour. I'm currently using LibreOffice 7.4.3.2 > 1048a8393ae2eeec98dff31b5c133c5f1d08b890 on macOS Monterey on an Intel Mac. > In order avoid this bug, to I have to continually remove the user settings > folder stored in ~/Library/Application Support/LibreOffice > > I am bored to have to continually delete the settings and I cannot configure > LibreOffice. > > It's like the the registrymodifications.xcu configuration file is getting > corrupted by the time making LibreOffice to hang. > If I delete this file and only this file, LibreOffice works well again. Looking at the attachment 184299, I think that this bug is caused by the same bug that I posted a patch for earlier today: https://bugs.documentfoundation.org/show_bug.cgi?id=148435#c82 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148051] Mac: Crashings for unkown reasons, despite reset user profile etc.
https://bugs.documentfoundation.org/show_bug.cgi?id=148051 Patrick Luby changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8435 --- Comment #39 from Patrick Luby --- Looking at the attachment 178950, I think that this bug is caused by the same bug that I posted a patch for earlier today: https://bugs.documentfoundation.org/show_bug.cgi?id=148435#c82 *** This bug has been marked as a duplicate of bug 148435 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152550] Drop the "Basic Fonts" option dialogs
https://bugs.documentfoundation.org/show_bug.cgi?id=152550 --- Comment #19 from Eyal Rozenberg --- (In reply to Mike Kaganski from comment #6) > Remove any given property from a given ODF, and the program would need to use > some default. If there is a configurable setting for it, the default value > could (?) be obtained from there Or a hardcoded default should be used. Use > of > hardcoded default instead of a configurable setting has its own pros, like > making documents more predictable So, why not just "combine" the hard-coded defaults, configurable defaults, and template-based creation? When an LO module starts, and if there is no default template - create a template (with default-default values) for the user, and make it the default template. From then on, you only allow a replacement of the default template, never a simple "de-selection" into a no-default-template state. And no more use of registrymodifications.xcu for any of this stuff. Benefits: 1. The "root defaults" are fully configurable (not just fonts - everything). 2. No need for special UI for editing the "root defaults" - you set them by editing the default template. 3. If a user hasn't touched the default template file, then they're using those hard-coded defaults - which have simply been copied into the template. 4. Can keep the hard-coded defaults out of the code: Just have a default-default-template file, part of the LO distribution but not in the editable templates directory (or hide it inside an .so / .dll or whatever). So, no code paths involving hard-coded values, just a check for existence of a default template. 5. Can forget about that part of the "registry" with the configurable defaults. Detriments: 1. It's slower to use a template than hard-coded values. But - we already some configurable defaults... 2. Some may argue that the specific default font settings we now have are more accessible to novice users then locating the default template, opening it for editing, and making changes to a bunch of default styles. 3. Transition from current scheme of things may be a bit confusing/inconvenient, may have some tombstone definitions in the registry etc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146598] Freezing when using cut, copy, or paste on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=146598 --- Comment #25 from Patrick Luby --- (In reply to steve from comment #8) > Persisting on master. Just happened when pasting a URL in writer in > Hyperlink dialog into URL field. However, this is a general problem > affecting all components. > > After force quit seeing crash report (1 year): > https://bin.disroot.org/ > ?72c20a0728884d89#HhMcgCMwwo7ZSTe2WWbjix2YQjPnEWAdkGfzjduyh5sZ Looking at the above report, I think that this bug is caused by the same bug that I posted a patch for earlier today: https://bugs.documentfoundation.org/show_bug.cgi?id=148435#c82 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151704] FILEOPEN DOC/X Incorrect table cell height when width is very thin
https://bugs.documentfoundation.org/show_bug.cgi?id=151704 Justin L changed: What|Removed |Added Summary|FILEOPEN DOC/X Incorrect|FILEOPEN DOC/X Incorrect |table cell height when |table cell height when |grid-after is faked |width is very thin Keywords|regression |bisected --- Comment #2 from Justin L --- In lcl_CalcMinCellHeight, we get nLowHeight = Height of pLow->getFrameArea() of 240. That sounds very much like a default value. Yup - that is done in SwTextFrame::Format when GetWidth <= 0 - it also grows or shrinks the frameHeight to 240. But this is VERY generic code. Clearly this is not a true regression, but just a consequence. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152661] "Hybrid PDF" must share embedded media between the ODT and the proper PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=152661 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=95 ||328 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95328] Hybrid PDF -- implement PDF 1.4 level support for Embedded File Streams to expose ODF object stream as Attachment to the PDF document
https://bugs.documentfoundation.org/show_bug.cgi?id=95328 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2661 --- Comment #12 from Eyal Rozenberg --- Speaking of PDF format compatibility... see also bug 152661 for a stronger ask. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103378] [META] PDF export bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103378 Eyal Rozenberg changed: What|Removed |Added Depends on||152661 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152661 [Bug 152661] "Hybrid PDF" must share embedded media between the ODT and the proper PDF -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152661] "Hybrid PDF" must share embedded media between the ODT and the proper PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=152661 Eyal Rozenberg changed: What|Removed |Added Blocks||103378 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103378 [Bug 103378] [META] PDF export bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152661] New: "Hybrid PDF" must share embedded media between the ODT and the proper PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=152661 Bug ID: 152661 Summary: "Hybrid PDF" must share embedded media between the ODT and the proper PDF Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Printing and PDF export Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com If we take the LibreOffice English User's Guide (from https://documentation.libreoffice.org/en/english-documentation/ ), and export it to a PDF with the default options, the result takes up about 20 MB of space. If we export it as a Hybrid PDF, it takes up 45.3 MB of space. That's totally excessive. It seems as though the full ODT, lock stock and barrol, is attached to the PDF. Instead, LO should arrange it so that as much of the information - at the very least entities like embedded images, fonts and such - with the proper PDF. With my example, the (compressed) ODT without the image takes up around 683 KB. I would therefore expect the Hybrid PDF to take up less than 21 MB. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149527] Calc crashes when scroll up and down quickly within a document, with Skia, not in Safe mode.
https://bugs.documentfoundation.org/show_bug.cgi?id=149527 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2649 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152649] Crash with activated SKIA Option
https://bugs.documentfoundation.org/show_bug.cgi?id=152649 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||9527 --- Comment #2 from Telesto --- Sounds like bug 149527 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152660] New: link to text formula help from the formula type form field (calculate with document statistics like word count)
https://bugs.documentfoundation.org/show_bug.cgi?id=152660 Bug ID: 152660 Summary: link to text formula help from the formula type form field (calculate with document statistics like word count) Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Documentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cl...@documentfoundation.org CC: olivier.hal...@libreoffice.org See https://ask.libreoffice.org/t/how-can-i-calculate-a-corrected-wordcount-in-a-field/20653/4?u=cloph It is not obvious how to do that, so I guess it would help to extend the description of the formula form field ( https://help.libreoffice.org/latest/en-US/text/swriter/01/04090005.html?=WRITER=UNIX ) to mention that the formula can contain the functions and variables as defined in the help for formulas in writer, notably the statistic fields. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 Eyal Rozenberg changed: What|Removed |Added Blocks||103407 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103407 [Bug 103407] [META] Unify behaviour and functions across apps -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103407] [META] Unify behaviour and functions across apps
https://bugs.documentfoundation.org/show_bug.cgi?id=103407 Eyal Rozenberg changed: What|Removed |Added Depends on||152652 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152652 [Bug 152652] [META] Introduce style categories missing in Impress/Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89369] Introduce Drawing object styles (shapes, textboxes...) to Writer & Calc like in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=89369 Eyal Rozenberg changed: What|Removed |Added CC||eyalr...@gmx.com Summary|Add support for drawing |Introduce Drawing object |styles (shapes and |styles (shapes, |textboxes) to Writer and|textboxes...) to Writer & |Calc|Calc like in Impress/Draw --- Comment #27 from Eyal Rozenberg --- Some style categories are present in Writer but not in Impress/Draw (like Character and Paragraph Styles; see meta-bug 152652), and for some - it is the other way around, like Drawing Object styles. We should definitely have a wide common denominator in term of style categories. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Patrick Luby changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |plub...@neooffice.org |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Patrick Luby changed: What|Removed |Added Status|VERIFIED|RESOLVED CC||plub...@neooffice.org --- Comment #82 from Patrick Luby --- I think I may have finally figured out what is causing this bug and I have posted the following patch: https://gerrit.libreoffice.org/c/core/+/144786 In theory, the above patch should not only fix this bug, but also the various other macOS hanging bugs that have the following two lines at the bottom of the first thread's stack like in attachment 184139: Task::Start(bool) std::mutex::lock() The patch needs still needs to be reviewed and tested before it appears in a nightly build. But if there any people who have a macOS LibreOffice build that can test the patch, that would be very much appreciated. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152659] Lock up then crash
https://bugs.documentfoundation.org/show_bug.cgi?id=152659 --- Comment #1 from wi...@2dsz.com --- Created attachment 184332 --> https://bugs.documentfoundation.org/attachment.cgi?id=184332=edit Help/About grab Build: https://git.libreoffice.org/core/+log/1048a8393ae2eeec98dff31b5c133c5f1d08b890 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias|style_support |style_additions -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias||style_support -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias|style, support | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias||sdraw, style, support -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias|-, (Impress/Draw), | |Impress/Draw, sdraw, Style, | |support | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias||Impress/Draw -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152658] Calc Autofilter "loses track" of entries when they are changed, hiding them when the filter is examined
https://bugs.documentfoundation.org/show_bug.cgi?id=152658 --- Comment #7 from Colin --- (In reply to m.a.riosv from comment #6) > Don't need to convince me. Let see if someone else agrees with you, that's > all. (In reply to m.a.riosv from comment #2) > Sorry, but what is the criteria to get 75 selected? > You are selecting from a list, why it should be re-selected after the change? > The standard filter can do it, and seems to me, it works fine. Sorry to reflect on this at such a late stage but you should be aware that any action in the standard filters like > With 'Field name' 'D' '=' 'Not empty' Will override and negate any prior selections on any of the slicers on any column - All you will ever get is what matches the standard filter setting for column D -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias||sdraw, (Impress/Draw), -, ||Style, support -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152654] Introduce List Styles in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152654 --- Comment #1 from Eyal Rozenberg --- Rafael, since you filed bug 137297, would you mind confirming? Or - do you think we need more discussion on this? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152659] New: Lock up then crash
https://bugs.documentfoundation.org/show_bug.cgi?id=152659 Bug ID: 152659 Summary: Lock up then crash Product: LibreOffice Version: 7.4.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: wi...@2dsz.com Description: Using Version 7.4.3.2 (x64) on Chrome browser. Laptop lock up occurs after a few minutes of use. Have to wait for crash before using recover file. This is with LibreOffice Calc. HP Envy laptop, Intel I7. Recover file works OK. Thanks Steps to Reproduce: 1.Open existing file 2.make entries and edits for a few minutes include edit comments 3.Lock up occurs, wait for crash, recover file Actual Results: Laptop locks up Brief unlock Libre crashes Expected Results: File should stay open for editing Reproducible: Always User Profile Reset: No Additional Info: Can't copy/paste Help/About -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152653] Introduce proper Paragraph Style support in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152653 Eyal Rozenberg changed: What|Removed |Added Severity|enhancement |normal Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #2 from Eyal Rozenberg --- (In reply to m.a.riosv from comment #1) > You have not assigned to yourself for solving it. ... hence it's not "ASSIGNED". > So someone else must set up as 'new' It's a split-up of a NEW issue for both CS and PS, both of which were recognized as desirable - so, two NEW bugs. Other bugs - Slide style, Table styles - are UNCONFIRMED. > And IMO it's a request for enhancement. For PS - It isn't, since it's an existing ODF feature, which PowerPoint supports, so it's just missing, not just that it would be better to have it. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152652] [META] Introduce style categories missing in Impress/Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=152652 V Stuart Foote changed: What|Removed |Added Alias|Impress-Missing-Style-Categ | |ories | Keywords||needsUXEval CC||vsfo...@libreoffice.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152655] Introduce a Slide/Page style category in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152655 V Stuart Foote changed: What|Removed |Added Keywords||needsUXEval CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||vsfo...@libreoffice.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152658] Calc Autofilter "loses track" of entries when they are changed, hiding them when the filter is examined
https://bugs.documentfoundation.org/show_bug.cgi?id=152658 --- Comment #6 from m.a.riosv --- Don't need to convince me. Let see if someone else agrees with you, that's all. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152658] Calc Autofilter "loses track" of entries when they are changed, hiding them when the filter is examined
https://bugs.documentfoundation.org/show_bug.cgi?id=152658 --- Comment #5 from Colin --- (In reply to m.a.riosv from comment #4) > Sorry, but I don't know what assures the new value meets the criteria for to > be selected in the list. > So for me not a bug. Did you observe the effect on the file when you change the value from 74 to 75? It must just be the same as adding a new row with the value of 75. Does LO exclude the new row just because 75 doesn't already exist in the index? Try another angle; Set the filter status to everything Add the value 12 to the bottom of the list Inspect the filter values and 12 is selected Now set the filter to exclude blanks Add the value 13 to the bottom of the list Inspect the filter values and 13 is deselected Did you change the filter from ignore blanks to ignore blanks AND any numbers between 12.1 and 14? What would you expect to happen if you cut and pasted 500 new entries to the bottom of the list? Again, for the record, Excel includes them and if the overarching desire is to be Excel compatible then I'm sorry to say it's failing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152656] "Drawing Style" should be renamed "Drawing Object Style"
https://bugs.documentfoundation.org/show_bug.cgi?id=152656 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Keywords||needsUXEval --- Comment #1 from V Stuart Foote --- +1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72367] FILESAVE: Z-Order of picture and text shapes doesn't save (or load) correctly in ODF
https://bugs.documentfoundation.org/show_bug.cgi?id=72367 mauricio changed: What|Removed |Added Version|Inherited From OOo |7.4.3.2 release Hardware|All |x86-64 (AMD64) OS|All |Windows (All) --- Comment #10 from mauricio --- (In reply to Justin L from comment #9) > repro 7.3+ Still reproducible with Version: 7.4.3.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152658] Calc Autofilter "loses track" of entries when they are changed, hiding them when the filter is examined
https://bugs.documentfoundation.org/show_bug.cgi?id=152658 --- Comment #4 from m.a.riosv --- Sorry, but I don't know what assures the new value meets the criteria for to be selected in the list. So for me not a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 32249] Make it easier to edit text in imported PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=32249 --- Comment #36 from V Stuart Foote --- (In reply to Eyal Rozenberg from comment #35) > 3. For the specific case of LO being the originator of the PDF, we could > consider - and that is out-of-scope here I suppose - embedding auxiliary > information into the PDF which allows for perfect or near-perfect > reconstitution of the original LO document. > Actually we already provide that with the source ODF inserted as a data stream to our PDF export--we call it a "Hybrid PDF". Although some potential to improve the visibility of the ODF data stream beyond LibreOffice's handling, as for bug 95328 and making the ODF a proper PDF attachment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152658] Calc Autofilter "loses track" of entries when they are changed, hiding them when the filter is examined
https://bugs.documentfoundation.org/show_bug.cgi?id=152658 --- Comment #3 from Colin --- (In reply to m.a.riosv from comment #2) > Sorry, but what is the criteria to get 75 selected? What is the criteria for deselecting it? If I add a line to the bottom of the array it's automatically included in both Excel and LO. If I set an Excel sheet in exactly the same manner as I did this LO sheet then Excel doesn't deselect the entry when it's edited. It is automatically included because there has been no exclusion by the user - I repeat NO exclusion by the user. > You are selecting from a list, why it should be re-selected after the change? NO, perhaps my description didn't make it clear - I made a change to an existing entry and then examined the list for other aspects and the moment I exited, LO decided of it's own volition to ignore the value because LO of it's own volition decided to deselect that new value. Excel doesn't deselect the value of it's own volition - that is the users' prerogative. I also believe that this is a NEW "feature" because I have spent two years performing the operation of amending values and hiding nulls but only recently has it started hiding real values. Initially, I thought perhaps it was me and my memory but then I performed the same task on Excel and discovered that it wasn't me going crazy, it is LO misbehaving. > The standard filter can do it, and seems to me, it works fine. > With 'Field name' 'D' '=' 'Not empty' Why would I need to play with standard filters to remedy a rogue action by LO? The slicer allows me to specify if I wish to exclude any or many items and include or exclude empty, null or zero cell values. What the slicer should not do is make those choices on behalf of the user. If I have a list of items where the value may change and I don't wish to see the ones that have reduced to zero I can exclude zero values when I filter. What should NEVER happen is that if I reduce the number then it is completely removed even though it has a value. Go shopping with 500 Euros in your wallet. Buy a shirt for 50 Euros pay for it. Look in your wallet at the next shop and discover your wallet has decided you no longer have the remaining 450 Euros. Is that how LO is supposed to work`? RE-READ the first line. If the autofilter is not set to exclude blanks it ditches the 74 and retains the selection of 75 - and that value remains in the subtotal regardless of how many times I examine the filter or deselect 225 or 450 or 62357,25 OR how many times I adjust the other slicers which only exclude entries from the same row -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152633] colleagues using MSO 365 can not open my .docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=152633 --- Comment #9 from Buovjaga --- (In reply to Tom from comment #8) > Thank you very much to all of you who have commented and tried to help! Are > you recommending I use Libre Office 7.5 or 7.6 instead of my 7.4.2.3? Can I > get either LO 7.5 or 7.6 by torrent? The download link one commenter gave > took too many hours to download and failed repeatedly. The company I work > for has ten people and everyone works from home. I really really do not want > to have to use Windows and MSO365, but this problem makes me feel like I may > have to ask the boss to buy them for me. No, we are not recommending it. It would just be useful to hear of your own test result with an unreleased version. The unreleased version installs separately and will not mess with your stable version. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127588] BACKGROUND COLOR IN TABLE: Error message when pasting hex value "The inserted text exceeded the maximum length of this text field."
https://bugs.documentfoundation.org/show_bug.cgi?id=127588 Andreas Heinisch changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |andreas.heini...@yahoo.de |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152633] colleagues using MSO 365 can not open my .docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=152633 --- Comment #8 from Tom --- Thank you very much to all of you who have commented and tried to help! Are you recommending I use Libre Office 7.5 or 7.6 instead of my 7.4.2.3? Can I get either LO 7.5 or 7.6 by torrent? The download link one commenter gave took too many hours to download and failed repeatedly. The company I work for has ten people and everyone works from home. I really really do not want to have to use Windows and MSO365, but this problem makes me feel like I may have to ask the boss to buy them for me. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152658] Calc Autofilter "loses track" of entries when they are changed, hiding them when the filter is examined
https://bugs.documentfoundation.org/show_bug.cgi?id=152658 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Sorry, but what is the criteria to get 75 selected? You are selecting from a list, why it should be re-selected after the change? The standard filter can do it, and seems to me, it works fine. With 'Field name' 'D' '=' 'Not empty' -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146598] Freezing when using cut, copy, or paste on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=146598 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||8435 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148435] LibreOffice on macOS hangs on using window snapping / window manager (BetterTouchTool, Rectangle, Raycast, Amethyst, ...) or any other redraw, context switch, etc, from
https://bugs.documentfoundation.org/show_bug.cgi?id=148435 Alex Thurgood changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6598 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146598] Freezing when using cut, copy, or paste on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=146598 --- Comment #24 from Alex Thurgood --- (In reply to TH from comment #23) > Problem still exists > > Version: 7.4.3.2 / LibreOffice Community > Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 > CPU threads: 12; OS: Mac OS X 11.7.2; UI render: default; VCL: osx > Locale: de-DE (de_DE.UTF-8); UI: de-DE > Calc: threaded @TH : please try with either: LibreOffice 7.4.4 pre-release or LibreOffice 7.5 beta pre-release. or alternatively, wait until 7.4.4 is released in January. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152404] Crash in Writer when using Japanese Hiragana input method and shortcut Ctrl+Alt+C to insert a new comment while there is uncommitted text
https://bugs.documentfoundation.org/show_bug.cgi?id=152404 --- Comment #5 from Patrick Luby --- Note: this bug has been already fixed in macOS in the following patch: https://cgit.freedesktop.org/libreoffice/core/commit/vcl/osx/vclnsapp.mm?id=9ee57f36e26373ee7144d076c93c3462c4fc7110 The above patch essentially calls SalFrame::EndExtTextInput(EndExtTextInputFlags::Complete) just before dispatching any key events with the Command key pressed. I assume that a similar fix could be used for Windows and Linux by making the same call just before dispatching key events with the Control key pressed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152645] LibreOffice interface improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=152645 V Stuart Foote changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Ever confirmed|1 |0 Keywords||needsUXEval Status|REOPENED|UNCONFIRMED --- Comment #12 from V Stuart Foote --- this is issue of bug 37134, doing an MDI "multi-document interface" otherwise nothing new or substantive in the mock-ups IHMO => DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49787] Formatting: Allow different slide / page styles (orientation, size) in a single Drawing document
https://bugs.documentfoundation.org/show_bug.cgi?id=49787 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2655 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152655] Introduce a Slide/Page style category in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=152655 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=49 ||787 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146598] Freezing when using cut, copy, or paste on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=146598 --- Comment #23 from TH --- Problem still exists Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 12; OS: Mac OS X 11.7.2; UI render: default; VCL: osx Locale: de-DE (de_DE.UTF-8); UI: de-DE Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152519] SurroundingText is not working in kf5 VCL
https://bugs.documentfoundation.org/show_bug.cgi?id=152519 Michael Weghorn changed: What|Removed |Added Status|REOPENED|NEW --- Comment #10 from Michael Weghorn --- (In reply to trmdi from comment #6) > Probably something's wrong with your setup. It does support that here on my > openSUSE Tumbleweed, Kate 22.12.0 Indeed, was apparently some problem with my setup, since I was using the same Kate version. It works now. Interestingly, I explicitly have to unset GTK_IM_MODULE (or set it to an empty string) because GTK_IM_MODULE=fcitx breaks the LO Writer use case with gtk3 (still works with Calc or gedit, though...). (In reply to Xuetian Weng from comment #9) > While it is possible to implement a polling like logic. Retrieving > surrounding text is an expensive query, so I'd prefer libreoffice to notify > the change instead of letting input method poll it. > > Also, the implementation itself seems not working properly. Even if I tried > to hack fcitx5-qt to poll the surrounding text by explicitly query the > object, it return value for inputMethodQuery(Qt::ImSurroundingText) is still > QVariant(Invalid). > > So despite of adding qApp->inputMethod()->update(Qt::ImSurroundingText | > Qt::ImCursorPosition | Qt::ImAnchorPosition) to a proper place maybe also > check if this lcl_retrieveSurrounding actually works. > https://github.com/LibreOffice/core/blob/ > d57836db76fcf3133e6eb54d264c774911015e08/vcl/qt5/QtWidget.cxx#L897 > > Gtk counterpart seems to use a different approach for retrieving surrounding > https://github.com/LibreOffice/core/blob/ > 83485052e6cac574754191c59371dbc41383b810/vcl/unx/gtk3/gtkframe.cxx#L5824 Thank you so much, this is extremely helpful! I have experimented a bit locally and have had a first quick-and-dirty version that somewhat works (but breaks other things), but needs more work for a proper solution. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152404] Crash in Writer when using Japanese Hiragana input method and shortcut Ctrl+Alt+C to insert a new comment while there is uncommitted text
https://bugs.documentfoundation.org/show_bug.cgi?id=152404 --- Comment #4 from Aron Budea --- Created attachment 184331 --> https://bugs.documentfoundation.org/attachment.cgi?id=184331=edit Backtrace -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152404] Crash in Writer when using Japanese Hiragana input method and shortcut Ctrl+Alt+C to insert a new comment while there is uncommitted text
https://bugs.documentfoundation.org/show_bug.cgi?id=152404 Aron Budea changed: What|Removed |Added Ever confirmed|0 |1 CC||aron.bu...@gmail.com Version|7.5.0.0 alpha1+ |4.0.0.3 release Status|UNCONFIRMED |NEW Keywords||haveBacktrace --- Comment #3 from Aron Budea --- Confirmed using LO 7.6.0.0.alpha0+ (40db42be1d8fd0f9c6c8c5ba3767ddb9ee2034c2), 4.0.0.3 / Windows. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109527] [META] Spell check dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109527 kit...@tutanota.com changed: What|Removed |Added CC||kit...@tutanota.com --- Comment #1 from kit...@tutanota.com --- What is this all about and why was I notified about it? -- You are receiving this mail because: You are the assignee for the bug.
