[Libreoffice-bugs] [Bug 156372] The height of the header is larger when compared to MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=156372 --- Comment #3 from SATYA SRINIVAS K --- Created attachment 188463 --> https://bugs.documentfoundation.org/attachment.cgi?id=188463=edit Header Size comparision -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156372] The height of the header is larger when compared to MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=156372 --- Comment #2 from SATYA SRINIVAS K --- Created attachment 188462 --> https://bugs.documentfoundation.org/attachment.cgi?id=188462=edit last Para moved to next page -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156372] The height of the header is larger when compared to MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=156372 --- Comment #1 from SATYA SRINIVAS K --- Created attachment 188461 --> https://bugs.documentfoundation.org/attachment.cgi?id=188461=edit Simple Doc to reproduce -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156372] New: The height of the header is larger when compared to MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=156372 Bug ID: 156372 Summary: The height of the header is larger when compared to MSO Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: skompe...@opentext.com Description: The content from the first page is moving to the next page due to the large header height. Steps to Reproduce: 1.Open the attached "Header_Size_Simple.doc" in both LO and MS word. 2.Observe that the last paragraph on the first page is moved to the next page. 3.Observe that the size of the header in both MSO and LO. Actual Results: The content from first page is moved to next page due to the header size. Expected Results: LO should render same as MS word. Reproducible: Always User Profile Reset: Yes Additional Info: Attachments:"Header_Size_Simple.doc","Header_Size_Issue.png" and "Para_moved_Issue.png" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144512] Please make timing of auto-save a per-document action
https://bugs.documentfoundation.org/show_bug.cgi?id=144512 --- Comment #21 from Mike Kaganski --- (In reply to Luke Kendall from comment #20) > I'll try. I'm assuming it's a 7.5 series build? No :) it is a master build. https://dev-builds.libreoffice.org/daily/master/current.html But it seems, that there's no builds for Linux from today. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156343] Scrollbar slider size does not change on Mouse-Over
https://bugs.documentfoundation.org/show_bug.cgi?id=156343 Bernhard changed: What|Removed |Added Summary|Scrollbars size does not|Scrollbar slider size does |change on Mouse-Over|not change on Mouse-Over -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155891] Option to Force pressing F2 (or Enter) to switch to cell edit mode as ONLY mean
https://bugs.documentfoundation.org/show_bug.cgi?id=155891 ady changed: What|Removed |Added Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155891] Option to Force pressing F2 (or Enter) to switch to cell edit mode as ONLY mean
https://bugs.documentfoundation.org/show_bug.cgi?id=155891 ady changed: What|Removed |Added Resolution|NOTABUG |--- Status|RESOLVED|UNCONFIRMED --- Comment #3 from ady --- (In reply to danomois from comment #2) > this is not a bug. @danomois, this is set as ENHANCEMENT request, not reporting a bug of an already-established feature/behavior. Someone might think this is worth implementing, a discussion and a decision might arise. I am changing the status back from NAB to UNCONFIRMED, as it was before. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156229] Calc- Select Categories in Theme does not apply changes to sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=156229 ady changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #3 from ady --- Suggestion: 1. Open a new Calc spreadsheet. 2. Menu Styles > Manage Styles (the Style side bar opens) 3. A1: Double click on some style in the side bar, e.g Card > Card B 4. Menu Format > Spreadsheet Theme 5. Click once on each theme; for each theme, A1 changes its background color (for the "Card B" cell style, for example). The content of the official Help might need some clarification, or better wording, or examples. https://help.libreoffice.org/latest/en-US/text/scalc/guide/design.html If all this works for you, then maybe a new report to request / suggest improvements to the help content would be better than having this report bug 156229. Please test and confirm. Setting to NEEDINFO. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156371] New: Compressing the CJK punctuations at the beginning of line
https://bugs.documentfoundation.org/show_bug.cgi?id=156371 Bug ID: 156371 Summary: Compressing the CJK punctuations at the beginning of line Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vicxp0...@163.com Description: The punctuations (especially those CJK ones) which stays at the beginning of any lines, should have the ability to be automatically compressed/indented, so that they look "aligned" to the left side of the paragraph. Writer has by far no such function, while it's very commercially demanded, comparing to Word/InDesign. Steps to Reproduce: 1.Start a paragraph with a CJK quotation mark (e.g.). 2.Or, insert into the middle of a sentence, and to make sure the quotaion mark right wraps into the beginning of a line. Actual Results: The quotation mark (e.g.) looks like "concaved" into the paragraph's left side, which makes the document looks "untrained". Expected Results: Should be able to compress such puntuations. Reproducible: Always User Profile Reset: No Additional Info: Could reference to Word/Indesign, which has such functionality. In Word, it's a checkbox labeled "Allow punctuations at the start of a line to compress", found in "Paragraph" dialogue, "Asian Topography" tab. Could also reference to open-source typeface management documentations for detail. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156370] New: Assigning a paragraph style causes the cursor jumps back to section title
https://bugs.documentfoundation.org/show_bug.cgi?id=156370 Bug ID: 156370 Summary: Assigning a paragraph style causes the cursor jumps back to section title Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: minor Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vicxp0...@163.com Description: Assigning a paragraph style causes the cursor jumps back to the current section's title/heading, leading to confusion of where we were at. Steps to Reproduce: 0.No matter which type of "User Interface" is in. 1.Prepare a long section of article, which should be taller than the screen. 2.Assign any "Heading" styles to the title. 3.Scroll down by some distance, to ensure that the title has passed above screen. 4.Try to assign any paragraph style to any body part of the article. Actual Results: The screen immediately jumps back to the title/heading paragraph of the article, causes great confusion, since you have to reallocate from where your focus was at. Expected Results: Don't jump to cursor immediately. Reproducible: Always User Profile Reset: No Additional Info: Please allow the cursor to be off-screen should solve similar issues. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156364] Fonts are displayed slightly different on Linux, which causes the characters to overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=156364 --- Comment #3 from خالد حسني --- Looks like difference in DPI to me, does the Windows machine have a hidpi screen and Linux machine has a regular one? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144512] Please make timing of auto-save a per-document action
https://bugs.documentfoundation.org/show_bug.cgi?id=144512 --- Comment #20 from Luke Kendall --- I'll try. I'm assuming it's a 7.5 series build? So I'm looking in https://dev-builds.libreoffice.org/daily/libreoffice-7-5/Linux-rpm_deb-x86_64@tb87-TDF/ which includes a directory named 2023-07-18_16.37.24/ but I couldn't see anything labelled 24.2.0 It's a little difficult for me at the moment as I may have to leave home for a few days due to family health problems, but I'll see what I can do. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156162] Unhelpful error message when trying to install an extension over an existing macro library
https://bugs.documentfoundation.org/show_bug.cgi?id=156162 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 155337] Writer Has Repeatable Crash
https://bugs.documentfoundation.org/show_bug.cgi?id=155337 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155891] Option to Force pressing F2 (or Enter) to switch to cell edit mode as ONLY mean
https://bugs.documentfoundation.org/show_bug.cgi?id=155891 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 156019] Headings are illegible when printing docx
https://bugs.documentfoundation.org/show_bug.cgi?id=156019 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156161] Organise Macros > Python requires JRE
https://bugs.documentfoundation.org/show_bug.cgi?id=156161 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 151792] In presenter view, Impress seems to remove formatting from notes
https://bugs.documentfoundation.org/show_bug.cgi?id=151792 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 155337] Writer Has Repeatable Crash
https://bugs.documentfoundation.org/show_bug.cgi?id=155337 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151747] Libreoffice crashes when selecting menu option
https://bugs.documentfoundation.org/show_bug.cgi?id=151747 --- Comment #10 from QA Administrators --- Dear Alex, 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 151747] Libreoffice crashes when selecting menu option
https://bugs.documentfoundation.org/show_bug.cgi?id=151747 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 147743] Crash on start
https://bugs.documentfoundation.org/show_bug.cgi?id=147743 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 152348] LibreOffice Writer crash after installing Help on 4GB memory RAM
https://bugs.documentfoundation.org/show_bug.cgi?id=152348 --- Comment #3 from QA Administrators --- Dear sberube, 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 147743] Crash on start
https://bugs.documentfoundation.org/show_bug.cgi?id=147743 --- Comment #5 from QA Administrators --- Dear GB, 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 145325] Weird behaviour when using custom cell height
https://bugs.documentfoundation.org/show_bug.cgi?id=145325 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 147554] Changing fonts within an app makes cursor disappear and app won't accept input
https://bugs.documentfoundation.org/show_bug.cgi?id=147554 --- Comment #3 from QA Administrators --- Dear dentar, 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 108364] [META] Table/Row/Column/Cell management function bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108364 Bug 108364 depends on bug 145325, which changed state. Bug 145325 Summary: Weird behaviour when using custom cell height https://bugs.documentfoundation.org/show_bug.cgi?id=145325 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145325] Weird behaviour when using custom cell height
https://bugs.documentfoundation.org/show_bug.cgi?id=145325 --- Comment #11 from QA Administrators --- Dear Perico Palotes, 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 149553] Problème d'ancrage image sur les pages, quand on supprime ou rajoute une page
https://bugs.documentfoundation.org/show_bug.cgi?id=149553 --- Comment #3 from QA Administrators --- Dear Launeau 85, 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 149403] Embedded videos 'disappear' when presentation is closed and reopened
https://bugs.documentfoundation.org/show_bug.cgi?id=149403 --- Comment #2 from QA Administrators --- Dear mfwyatt75, 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 147584] Freeze when I switch between windows of chrome ( or other ) and Libreoffice or when paste in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=147584 --- Comment #5 from QA Administrators --- Dear roman.hromada, 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 135832] UI: Configuring a bitmap to show on full page with custom position and size not easy to do/ user friendly
https://bugs.documentfoundation.org/show_bug.cgi?id=135832 --- Comment #6 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 112037] please add support for crash reporting
https://bugs.documentfoundation.org/show_bug.cgi?id=112037 --- Comment #5 from QA Administrators --- Dear vihsa, 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 98063] EDITING read-only mode allows cut and paste with mouse in Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=98063 --- Comment #11 from QA Administrators --- Dear Ryan Hankins, 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 141948] FILEOPEN DOCX chart's date axis format changed
https://bugs.documentfoundation.org/show_bug.cgi?id=141948 --- Comment #9 from QA Administrators --- Dear NISZ LibreOffice Team, 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 118695] Table number recognition not immediately disabled for cells where replacing took place previously
https://bugs.documentfoundation.org/show_bug.cgi?id=118695 --- Comment #4 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://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 105579] After certain actions comments in Calc point to the wrong cell
https://bugs.documentfoundation.org/show_bug.cgi?id=105579 --- Comment #17 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 156369] New: Tripple-Clicking causes jumping to the end of paragraph.
https://bugs.documentfoundation.org/show_bug.cgi?id=156369 Bug ID: 156369 Summary: Tripple-Clicking causes jumping to the end of paragraph. Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vicxp0...@163.com Description: When selecting a very-long paragraph by triple clicking at it, Writer always jumps to the end of the paragraph, causing uncomfortness of reading, compared to Word/Pages which will hold the position of screen. Steps to Reproduce: 1.Make a long paragraph which could overfit one screen. 2.Scroll up to ensure that the end of the paragraph is out of screen. 3.Try to tripple-click at the paragraph. Actual Results: The screen immediately scrolls to the end of the paragraph (where the cursor jumps to), instead of staying at where it was. Expected Results: Staying at where it was should be more friendly while reading or presenting. Reproducible: Always User Profile Reset: No Additional Info: Could take Word or Pages as examples. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156368] New: Watermark font not working if starts with CJK characters
https://bugs.documentfoundation.org/show_bug.cgi?id=156368 Bug ID: 156368 Summary: Watermark font not working if starts with CJK characters Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vicxp0...@163.com Description: Setting font for watermark does not working, if the watermark text starts with CJK characters. Steps to Reproduce: 1.Set a watermark, which the 1st character is CJK. 2.Set a font. 3.Apply to see. Actual Results: The font does not apply, *unless* have inserted a half-width character right before the CJK text. Expected Results: Needless to be starting with half-width characters. Reproducible: Always User Profile Reset: No Additional Info: NA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156367] New: Half-Width characters making the Double-Lined style wrap incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=156367 Bug ID: 156367 Summary: Half-Width characters making the Double-Lined style wrap incorrectly Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vicxp0...@163.com Description: If you insert any half-width character into a section of Double-Lined CJK text, it incorrectly wraps right behind the half-width string, disregarding position-of-line/page. Steps to Reproduce: 1. Define a character style which has "Double-Lined" style enabled. 2. Apply it to some of the CJK text. 3. Try to insert half-width characters into that text. Actual Results: It wraps immediately behind the half-width string, no matter where its position is to the line/page. Expected Results: Shouldn't wrap behind the half-width string. Reproducible: Always User Profile Reset: No Additional Info: Currently no walkaround. Happens on both Windows and Mac build. Other builds not tried. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156366] New: Writer: Double-lined charaters do not wrap lines correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=156366 Bug ID: 156366 Summary: Writer: Double-lined charaters do not wrap lines correctly Product: LibreOffice Version: 7.5.4.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vicxp0...@163.com Description: When editing the characters where have the "Double-Lined" style enabled, the line wrapping inside the doubled lined region goes stubborn and odd. Nearly-always-reproducible with CJK letters. Steps to Reproduce: 1. Define a Double-Lined character style. 2. Apply it to some characters, the long the better. 3. Let it cross the end of the line (ie. let the double-lined text wrap into two major lines). 4. Save the file. 5. Try to insert more chars into the double-lined text at its first major line, and see how the later characters wrap into the second major line. Actual Results: It seems that there is "stubborn" invisible line wrapping control marks refuse to change its position automatically. Expected Results: Should auto wrap as natually. Reproducible: Always User Profile Reset: No Additional Info: Current walkaround (but annoying): 1. Select the entire double-lined text; 2. Cut; 3. At position, paste as plain text. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155891] Option to Force pressing F2 (or Enter) to switch to cell edit mode as ONLY mean
https://bugs.documentfoundation.org/show_bug.cgi?id=155891 Daniel Moisio changed: What|Removed |Added CC||danielmoisiow...@gmail.com Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #2 from Daniel Moisio --- freeware, Interesting idea - and I get what you are asking for. However, this is not a bug. As for methods and alternatives - you noted a few that could work - but frankly having a button like f2, which is already used in calc work, suddenly be the guardian of edit-ability does not seem right because hypothetically you could accidentally hit f2 and edits would occur anyway. Hazards of end user computing type software in my view. Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156358] VIEWING: Calc AutoInput (pop up formula editing helper) hides the formula [Flatpak]
https://bugs.documentfoundation.org/show_bug.cgi?id=156358 Daniel Moisio changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #4 from Daniel Moisio --- Hi Moshpirit, I am marking need info because I can see your screenshot and with that behavior I would call it a bug if I could reproduce the problem. At least my version as below however is not producing the same behavior. As you see from the screenshot - the help pop-up is showing up on the top of the formula bar even with a single toolbar interface, but not covering the formula bar. I am frankly quite new to this and may be missing something that you inherit using Flatpak - but again I'm just not seeing it so maybe help with any more detail? Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 77fca616e0bd79e0b405fd0b3543cf8e94e15df3 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 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 156358] VIEWING: Calc AutoInput (pop up formula editing helper) hides the formula [Flatpak]
https://bugs.documentfoundation.org/show_bug.cgi?id=156358 --- Comment #3 from Daniel Moisio --- Created attachment 188460 --> https://bugs.documentfoundation.org/attachment.cgi?id=188460=edit formulahelper -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77999] [META] Autosave/Autorecovery/Backup copy issues
https://bugs.documentfoundation.org/show_bug.cgi?id=77999 Bug 77999 depends on bug 68565, which changed state. Bug 68565 Summary: Other: Request for capability to save .BAK files in same location as original document https://bugs.documentfoundation.org/show_bug.cgi?id=68565 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156229] Calc- Select Categories in Theme does not apply changes to sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=156229 Daniel Moisio changed: What|Removed |Added Ever confirmed|0 |1 CC||danielmoisiow...@gmail.com Status|UNCONFIRMED |NEW --- Comment #2 from Daniel Moisio --- Hello, Thank you for submitting this! I was able to recreate the issue using the version pasted below. I have no idea what some of the categories like Millennium, Nature, etc. are supposed to look like - but they are not applying any theme beyond standard so I would conclude it is a bug. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 77fca616e0bd79e0b405fd0b3543cf8e94e15df3 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 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 156243] AUTOCORRECT: with "Edit"->"Track Changes"->"Show" enabled, doing "Tools"->"AutoCorrect"->"Apply and Edit Changes"->"Accept All" fails to AutoCorrect last character in s
https://bugs.documentfoundation.org/show_bug.cgi?id=156243 Matt K changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |matt...@gmail.com |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156019] Headings are illegible when printing docx
https://bugs.documentfoundation.org/show_bug.cgi?id=156019 --- Comment #2 from Rob --- (In reply to Eyal Rozenberg from comment #1) > What kind of headings do you mean? If it's the styles Heading 1, Heading 2 > etc. - then I can't reproduce! And I have a Brother printer. > > I suspect the issue is more with your print driver (or rather, print driver > + desktop environment + operating system). Have you seen this on other > printers? When printing to PDFs? Yes I mean the styles Heading 1, 2, 3 etc. I didn't have another printer to test this on, but it didn't occur when printing to PDF. It also didn't occur when printing to the printer from PDFs. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156364] Fonts are displayed slightly different on Linux, which causes the characters to overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=156364 --- Comment #2 from Hossein --- Created attachment 188459 --> https://bugs.documentfoundation.org/attachment.cgi?id=188459=edit PDF output from LibreOffice on Linux As declared above, this is also for the reference. The difference is on display. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156364] Fonts are displayed slightly different on Linux, which causes the characters to overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=156364 --- Comment #1 from Hossein --- Created attachment 188458 --> https://bugs.documentfoundation.org/attachment.cgi?id=188458=edit PDF output from LibreOffice on Windows Please note that the difference is on display, and I see no difference in PDF output. I am putting the PDF files here for the reference. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38844] Reduce XOR rendering (search RasterOp::Xor)
https://bugs.documentfoundation.org/show_bug.cgi?id=38844 Hossein changed: What|Removed |Added Depends on||156365 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156365 [Bug 156365] Trails in typing cursor (dark mode) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156365] Trails in typing cursor (dark mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=156365 Hossein changed: What|Removed |Added Blocks||38844 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||2970 --- Comment #1 from Hossein --- I think the problem comes from XOR rendering as discussed below: tdf#38844 - Reduce XOR rendering (search RasterOp::Xor) https://bugs.documentfoundation.org/show_bug.cgi?id=38844 A similar (fixed) bug on direct cursor leaving trail: tdf#122970 - Direct cursor leaves screen trail with mouse pointer movement and no text https://bugs.documentfoundation.org/show_bug.cgi?id=122970 Therefore, I set this issue as a blocker for tdf#38844. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=38844 [Bug 38844] Reduce XOR rendering (search RasterOp::Xor) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 118591] [NEWHELP] Editing: F1 key press goes to missing page when chart object is in edit mode on Impress page
https://bugs.documentfoundation.org/show_bug.cgi?id=118591 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #6 from Rafael Lima --- When double-clicking the chart and pressing F1, it should redirect to: file:///usr/share/libreoffice/help/en-US/text/schart/main.html?DbPAR=CHART This patch fixes it: https://gerrit.libreoffice.org/c/help/+/154611 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156365] New: Trails in typing cursor (dark mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=156365 Bug ID: 156365 Summary: Trails in typing cursor (dark mode) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 188457 --> https://bugs.documentfoundation.org/attachment.cgi?id=188457=edit Trail of an old cursor alongside the actual cursor Description: While typing text in LibreOffice, sometimes a trail remains. This is mostly visible when using bidirectional text while dark mode is activated. Steps to Reproduce: 1. Type something in English or other language that is written from left to right like 'English'. 2. Then type something in Arabic/Persian, or other language that is written from right to left, like 'فارسی'. 3. Wait until the directional blinking cursor hides for a second or less as it blinks. 4. Be fast and move the cursor with arrow keys left or right. Actual Results: Trail of the cursor remains in the old place. This sometimes happen even when you type in a single language, but it is easier to reproduce with multiple directions. Expected Results: No trail of the cursor should remain in the old place. Reproducible: Always User Profile Reset: No Additional Info: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bb01ef3865c406f322d6e656faba2191aaeeb6da CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_DE); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155875 --- Comment #24 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/f94e18ea85ea872081a15b2414b395eec2fbbcf5 tdf#155875 Tab'd UI commands Writer/Insert in Help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155875] [LOCALHELP] - Writer - Help pages about dialogs should provide instructions for the Tabbed UI
https://bugs.documentfoundation.org/show_bug.cgi?id=155875 --- Comment #23 from Commit Notification --- Olivier Hallot committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/b2c510207a640e706857bb5fa716de56e0e55751 tdf#155875 Tab'd UI commands Writer/Insert in Help -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO
https://bugs.documentfoundation.org/show_bug.cgi?id=71732 Hossein changed: What|Removed |Added Depends on||156364 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156364 [Bug 156364] Fonts are displayed slightly different on Linux, which causes the characters to overlap -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156364] Fonts are displayed slightly different on Linux, which causes the characters to overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=156364 Hossein changed: What|Removed |Added Blocks||71732 CC||kha...@libreoffice.org Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=71732 [Bug 71732] [META] Bugs related to text rendering, typography and font features in LO -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156364] New: Fonts are displayed slightly different on Linux, which causes the characters to overlap
https://bugs.documentfoundation.org/show_bug.cgi?id=156364 Bug ID: 156364 Summary: Fonts are displayed slightly different on Linux, which causes the characters to overlap Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 188456 --> https://bugs.documentfoundation.org/attachment.cgi?id=188456=edit Comparing output in Linux and Windows Description: With Harfbuzz as the font rendering engine in LibreOffice, it is expected that font rendering output on display and print are the same on different platforms. But, in reality there are slight differences. For example, in this case fonts are displayed slightly different on Linux, which causes the characters to overlap. Steps to Reproduce: 1. Open attachment 188277 in LO Writer dev master on Windows 2. Open the same file in LO Writer dev master on Linux 3. Compare the outputs on Windows and Linux display Actual Results: The outputs on display are different, and the characters sometimes overlap. For example, in the last line the starting » falls on the next character, which is ب and there is not (slight) space between them. Please look at «به همین دلیل» and other places in the start of double quotes «». Expected Results: Output on display in different platforms should be similar, and anyway the characters should not overlap in different zoom levels. There should be a slight space between » and ب in the last line. For a comparison, the results are normalized (for size) and compared side by side in the attachment with 110% zoom level on both Windows and Linux. LO on Windows and Linux were built from the same git revision. Reproducible: Always User Profile Reset: No Additional Info: LO 24.2 dev master on Linux: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bb01ef3865c406f322d6e656faba2191aaeeb6da CPU threads: 12; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: CL threaded LO 24.2 dev master on Windows: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: bb01ef3865c406f322d6e656faba2191aaeeb6da CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96886] Allow to change mouse pointer into a "laser pointer" during slide show
https://bugs.documentfoundation.org/show_bug.cgi?id=96886 Rafael Lima changed: What|Removed |Added Summary|Support Laser Pen |Allow to change mouse ||pointer into a "laser ||pointer" during slide show -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96886] Support Laser Pen
https://bugs.documentfoundation.org/show_bug.cgi?id=96886 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #8 from Rafael Lima --- I was about to open a request for this as well. Luckily I found this ticket before. This is a very needed feature! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156363] Impress needs to offer image presets to allow quick image formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=156363 --- Comment #1 from Rafael Lima --- Created attachment 188455 --> https://bugs.documentfoundation.org/attachment.cgi?id=188455=edit PPTX file used in the screenshots This is the PPTX file shown in the screenshot. Open it in Impress and PowerPoint to notice that most of the formats are imported correctly. So why not make it easier for users to apply these formats as well? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156363] New: Impress needs to offer image presets to allow quick image formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=156363 Bug ID: 156363 Summary: Impress needs to offer image presets to allow quick image formatting Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com Created attachment 188454 --> https://bugs.documentfoundation.org/attachment.cgi?id=188454=edit Screenshot of the presets in MS PowerPoint MS PowerPoint offers a set of image formatting presets (see attached screenshot) which are very handy to quickly format images and make the slide look more polished. Most of these effects can be achieved in LO Impress, but without the presets it is a huge effort to format images in Impress as in the screenshot. The interesting part is that LO Impress can deal with most of these formats, since PPTX import works quite nicely, with exception of image shadows that are not imported (this is an topic for a different ticket). But in summary, if Impress can import these formats, this means that it can also create these formats as well. So I believe we should also offer a list of presets so that users can achieve good-looking image formats without all the work that is currently needed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156354] UI Basic dialog contents not visible in preview mode with scrollbars enabled
https://bugs.documentfoundation.org/show_bug.cgi?id=156354 --- Comment #2 from Rafael Lima --- FTR it is working fine in KF5 as well Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.5.4-0ubuntu0.23.04.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156361] Skia regression: semi-transparent .svg in .odp fails to render
https://bugs.documentfoundation.org/show_bug.cgi?id=156361 --- Comment #4 from Patrick Luby --- Random idea: if I understand how we are supposed to draw to mpAlphaVDev, I'd replace the following at source/outdev/bitmap.cxx:349: mpAlphaVDev->BlendBitmap(aTR, rAlpha); with the following pseudo-code: // Make copy of pSalAlphaBmp2 pSalAlphaBmp3 = pSalAlphaBmp2->Clone(); // not sure what the real code is here // Convert transparency to alpha pSalAlphaBmp2->Invert(); // Use the uninverted copy of pSalAlphaBmp2 for blending and, instead of // blending with the drawn bitmap, blend with opaque white. Assuming // mpAlphaVDev is grayscale already, blending the following should overwrite // mpAlphaVDev with grayscale. The SK_ColorWHITE should be darkened by the // two alpha masks so in the end we should have the new, inverted alpha mask. mpAlphaVDev->mpGraphics->BlendAlphaBitmap(aTR, SK_ColorWHITE, *pSalAlphaBmp, *pSalAlphaBmp3, *this)) // Convert alpha to transparency pSalAlphaBmp2->Invert(); return; I'll see if I can get something working in the next couple of days. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156360] EDITING - Please add an intuitive, easy-to-use draw feature in LibreOffice Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=156360 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||vsfo...@libreoffice.org Resolution|--- |INVALID --- Comment #1 from V Stuart Foote --- Sorry, the LibreOffice ODF Drawing editor draw module is already intuitive and easy to use. Please read the manual: https://books.libreoffice.org/en/DG74/DG74.html, and see chpt 2 for working with the rectangles and squares you probably would prefer over drawing a line feature (which also works, but requires change stroke to a custom weight 40 or 50pt). Also, if you filter "Opened" a PDF into Draw, that is an error prone work flow as all elements of the PDF will be parsed (with variable fidelity to original) onto the drawing canvas. It is much better to split your PDF into pages outside LibreOffice (e.g. with PDFtk or such) and then import each into Draw as a full image. And then apply graphics (lines or polygons) to "redact" things from the dra. As the default dpi resolution of the inserted PDF page defaults to 96dpi, if you need crisper resolution set the environment variable "PDFIMPORT_RESOLUTION_DPI" to some higher resolution, 600 DPI should suffice for this type workflow. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156362] FILEOPEN PPTX: vertical lines show much fainter
https://bugs.documentfoundation.org/show_bug.cgi?id=156362 --- Comment #2 from Gerald Pfeifer --- Created attachment 188453 --> https://bugs.documentfoundation.org/attachment.cgi?id=188453=edit Screenshot - LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156362] FILEOPEN PPTX: vertical lines show much fainter
https://bugs.documentfoundation.org/show_bug.cgi?id=156362 Gerald Pfeifer changed: What|Removed |Added Attachment #188452|Screenshot - LibreOffice|Screenshot - PowerPoint description|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156362] FILEOPEN PPTX: vertical lines show much fainter
https://bugs.documentfoundation.org/show_bug.cgi?id=156362 --- Comment #1 from Gerald Pfeifer --- Created attachment 188452 --> https://bugs.documentfoundation.org/attachment.cgi?id=188452=edit Screenshot - LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156362] New: FILEOPEN PPTX: vertical lines show much fainter
https://bugs.documentfoundation.org/show_bug.cgi?id=156362 Bug ID: 156362 Summary: FILEOPEN PPTX: vertical lines show much fainter 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: ger...@pfeifer.com Created attachment 188451 --> https://bugs.documentfoundation.org/attachment.cgi?id=188451=edit Sample document (PPTX) 1. Open the attached sample document. 2. Observe how the four vertical lines on the first slide appear much more faint and thinner (than in Office 365), -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151695] Errors when Running Scripts separately from the LibreOffice process
https://bugs.documentfoundation.org/show_bug.cgi?id=151695 Rafael Lima changed: What|Removed |Added Status|NEEDINFO|NEW CC||rafael.palma.l...@gmail.com --- Comment #2 from Rafael Lima --- I just stumbled upon this issue... I guess the reason you're getting this error is because you're using your OS python interpreter instead of using LibreOffice's own python interpreter. In this case, you need to set the proper PYTHONPATH export PYTHONPATH=/usr/lib/libreoffice/program:/usr/lib/python3/dist-packages Note: /usr/lib/libreoffice/program --> this is where scriptforge.py is located /usr/lib/python3/dist-packages --> this is where uno.py is located So you need to set this first before launching the interpreter. I'll update the help page accordingly: https://help.libreoffice.org/latest/en-US/text/sbasic/shared/03/sf_intro.html In summary, this is not a bug in ScriptForge nor LibreOffice... but an improvement in documentation is required. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #2 from jcs...@libreoffice.org --- (In reply to Robert Großkopf from comment #0) > Note: Views with internal HSQLDB will change the code while creating a view > from a query with > SELECT * FROM "tbl_person" > to > SELECT "tbl_Person"."ID", "tbl_Person"."Forename", "tbl_Person"."Surname" > FROM "tbl_Person" Who says that my definition should be changed field by field? If I want a field by field definition I can do it by myself, but I may want another approach, and why does the code have to change my definition? Maybe one of the reasons why Firebird is not moving forward is because we want it to do the same thing as HSQLDB *and in the same way*. I don't know if Firebird has more or less capabilities than HSQLDB, but what is surely wrong is to force it to do things the same way as another database, even when the results obtained in its own way are correct. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155337] Writer Has Repeatable Crash
https://bugs.documentfoundation.org/show_bug.cgi?id=155337 --- Comment #7 from BrendaEM --- Yikes! That's a lot of effort to verify a bug. Did we even need OpenGL acceleration in a desktop application? BTW, like many Windows laptop owners who actually use their laptop from battery, I do not use GPU acceleration on desktop applications. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109195 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156353 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156353 [Bug 156353] Footnotes disappear when using tracked changes in DOC or DOCX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156353 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156353 [Bug 156353] Footnotes disappear when using tracked changes in DOC or DOCX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Bug 83946 depends on bug 156353, which changed state. Bug 156353 Summary: Footnotes disappear when using tracked changes in DOC or DOCX https://bugs.documentfoundation.org/show_bug.cgi?id=156353 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109195 Bug 109195 depends on bug 156353, which changed state. Bug 156353 Summary: Footnotes disappear when using tracked changes in DOC or DOCX https://bugs.documentfoundation.org/show_bug.cgi?id=156353 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156353] Footnotes disappear when using tracked changes in DOC or DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=156353 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||109195, 83946 Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #4 from Stéphane Guillou (stragu) --- Thank you for testing 7.5.5 and reporting back, Camille. Glad the footnotes + tracked changes issue is now gone, closing as "works for me". Regarding the performance issue, please feel free to open a new report, preferably with an example file attached so we can test it and compare different version. Much appreciated! Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83946 [Bug 83946] [META] Tracking changes issues https://bugs.documentfoundation.org/show_bug.cgi?id=109195 [Bug 109195] [META] DOCX (OOXML) Footnote and Endnote bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156359] Mouse over on back ground window tool bar will bring that window to foreground
https://bugs.documentfoundation.org/show_bug.cgi?id=156359 --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to seinf...@jsli.org from comment #2) > I am using 7.5.4.2 ... perhaps there is a keyboard shortcut with which I'm > inadvertently turning on Direct Cursor, because it activated again today and > I definitely did not knowingly turn it on. (Seinfeld, I think you're after bug 156276, not this one) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156238] Python SFDatabases.Database.GetRows() crashes when no data is available
https://bugs.documentfoundation.org/show_bug.cgi?id=156238
Rafael Lima changed:
What|Removed |Added
CC||j...@ledure.be,
||rafael.palma.l...@gmail.com
--- Comment #3 from Rafael Lima ---
Hi, I have just run your script and it worked. Here's what I got as result:
< Python Shell >
>>> test1()
/home/rafael/Downloads/test.odb
Connection to Base successful
query ='CREATE TABLE "tickers" ("id" INTEGER GENERATED BY DEFAULT AS
IDENTITY(START WITH 0) NOT NULL PRIMARY KEY, "ticker" VARCHAR(50) NOT NULL,
"currency" VARCHAR(10) NOT NULL)'
Query executed successfully
query ='INSERT INTO "tickers" ("ticker", "currency") VALUES (\'a\', \'aa\')'
Query executed successfully
query ='SELECT "id" FROM "tickers" WHERE "ticker" = \'a\' '
Query executed successfully
execute_read_query(connection, query) =((0,),)
query ='SELECT "id" FROM "tickers" WHERE "ticker" = \'b\' '
Query executed successfully
execute_read_query(connection, query) =()
I simply opened the file, entered APSO Python sheel and ran "test1()".
Note that if you run the script for a second time, it will crash because the
ODB file will have been created.
@JPL any input in this issue?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156355] FIREBIRD: Views will show different fields when executed or opened for editing
https://bugs.documentfoundation.org/show_bug.cgi?id=156355 --- Comment #1 from jcs...@libreoffice.org --- I don't see any erroneous behavior. 1. Execute view viw_person --> Show 3 fields --> As you stated that is correct because the view was defined in that way (when the table had three fields). 2. Show the table --> has 4 field --> correct, the fourth field was added after the view definition. 3. Edit in SQLview. In this case you are doing a *new definition* of the view as the word *edit* suggest. If your *new* definition is "select *" you are selecting all the *current* fields in the table, that is, four fields, and you can see this if you execute the query. You are selecting *now* all the field that are *now* in the database, and fortunately you receive that, and not the fields that were in the table in any other moment 4. If you don't save the edit, the view will continue having 3 fields. 5. If you save the new definition, you will obtain all the fields (four) selected in the new definition -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156320] Conditional formats not copied properly
https://bugs.documentfoundation.org/show_bug.cgi?id=156320 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #8 from m.a.riosv --- Images shows a possible bug, but to reproduce it, a sample file it's needed. We don't need your original file, only with the minimal data to reproduce the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156320] Conditional formats not copied properly
https://bugs.documentfoundation.org/show_bug.cgi?id=156320 --- Comment #7 from laza...@iname.com --- It is a bug because the results are different and the duplicate sheet is not correct. Please see attached images. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156320] Conditional formats not copied properly
https://bugs.documentfoundation.org/show_bug.cgi?id=156320 m.a.riosv changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Ever confirmed|1 |0 Resolution|NOTABUG |--- --- Comment #6 from m.a.riosv --- Please attach a sample file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156320] Conditional formats not copied properly
https://bugs.documentfoundation.org/show_bug.cgi?id=156320 --- Comment #5 from laza...@iname.com --- Created attachment 188450 --> https://bugs.documentfoundation.org/attachment.cgi?id=188450=edit Incorrectly duplicated conditional formats -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156361] Skia regression: semi-transparent .svg in .odp fails to render
https://bugs.documentfoundation.org/show_bug.cgi?id=156361 Patrick Luby changed: What|Removed |Added CC||noelgran...@gmail.com, ||plub...@neooffice.org --- Comment #3 from Patrick Luby --- I haven't found what commit caused this change, but it appears that somewhere in the libreoffice-7-6 and master branches the code in vcl/source/outdev/bitmap.cxx:345 is getting called more frequently. The patch in https://bugs.documentfoundation.org/attachment.cgi?id=188448 disables one Skia alpha blending case and allows that case to fall through to the non-Skia slow alpha blending code. With this patch, the bug does *not* occur so it appears that the bug is in one or both of the following: SkiaSalGraphicsImpl::blendAlphaBitmap() SkiaSalGraphicsImpl::blendBitmap() -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156320] Conditional formats not copied properly
https://bugs.documentfoundation.org/show_bug.cgi?id=156320 --- Comment #4 from laza...@iname.com --- Created attachment 188449 --> https://bugs.documentfoundation.org/attachment.cgi?id=188449=edit Original individual column formats -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156361] Skia regression: semi-transparent .svg in .odp fails to render
https://bugs.documentfoundation.org/show_bug.cgi?id=156361 --- Comment #2 from Patrick Luby --- Created attachment 188448 --> https://bugs.documentfoundation.org/attachment.cgi?id=188448=edit Patch that disables Skia alpha blending and falls through to the non-Skia slow path -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156361] Skia regression: semi-transparent .svg in .odp fails to render
https://bugs.documentfoundation.org/show_bug.cgi?id=156361 --- Comment #1 from Patrick Luby --- Created attachment 188447 --> https://bugs.documentfoundation.org/attachment.cgi?id=188447=edit LibreOffice "about" logo with 50% transparency -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156361] New: Skia regression: semi-transparent .svg in .odp fails to render
https://bugs.documentfoundation.org/show_bug.cgi?id=156361 Bug ID: 156361 Summary: Skia regression: semi-transparent .svg in .odp fails to render Product: LibreOffice Version: 7.6.0.0 beta1+ Hardware: ARM OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: plub...@neooffice.org Description: With Skia/Metal or Skia/Raster enabled on macOS, the LibreOffice "about" image added in a presentation document with 50% transparency will fail to render (i.e. leave white areas) when running in a slideshow or printing. This behavior is in the libreoffice-7-6 and master branches. But it is not in LibreOffice 7.5.4. Steps to Reproduce: 1. Open the attached Impress document 2. Run a slideshow or print Actual Results: Several unexpected white areas are in the central part of the image. Expected Results: No white areas within the image. Reproducible: Always User Profile Reset: No Additional Info: This only occurs with Skia. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123877] "Hash incompatible" in calc spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=123877 --- Comment #21 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/24c52c6f8674a716f3f5102095421c97d03b19d8 related tdf#68565 tdf#123877 autosave: identify by args, not path It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 123877] "Hash incompatible" in calc spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=123877 Commit Notification changed: What|Removed |Added Whiteboard|target:7.4.0 target:7.3.4 |target:7.4.0 target:7.3.4 ||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 94472] Proposal for working in documents on two positions in side by side (so vertical) panes
https://bugs.documentfoundation.org/show_bug.cgi?id=94472 --- Comment #11 from epimitheas --- (In reply to Eyal Rozenberg from comment #6) > (In reply to Mike Kaganski from comment #5) > > I do not see how a request to have *tabs* corresponding to different parts > > of a document > > Which of the bugs talks about tabs? This one doesn't, and I don't see tabs > discussed in 31481 either. Can you better clarify how this bug is not > subsumed by 31481? > > > On an unrelated note: I fail to see what this feature offers over the > ability to have two windows editing/viewing the same document. epimitheas > does not seem to have answered this question when Cor asked it back in 2015. Just to clarify to Eyal Rozenberg and Cor, about what was the intended purpose of this feature back then (what it would offer to the user): If you are working on a multi-page document (f.e. a book, or a thesis) that consists of many sections/sub-sections/annexes etc, and you want to be able to view at the same time what you have typed in another part of your document for the same issue, then you can use this feature to save time (and effort). You can either use the chapters tabs to "jump" between different parts of the document that you are current using/modifying (not just jump to a predefined bookmark at the start of each chapter) or u can expand the viewport to view at the same time multiple chapters (at the exact point you wish to). It just offers convenience to the user that in a different case has to scroll up-down or remember where exactly in his document and what he has mentioned for the same matter. Eitherway, back then i used to work on big documents and seemed a good idea (my solution was to create a duplicate file and reopen it on a different window..). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152422] Inter-glyph jitter when underlining text with Skia rendering
https://bugs.documentfoundation.org/show_bug.cgi?id=152422 خالد حسني changed: What|Removed |Added Status|NEEDINFO|NEW --- Comment #10 from خالد حسني --- Probably spends on the screen resolution then, I have been testing on hipdi screens. I’ll try to test on a lodpi one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155337] Writer Has Repeatable Crash
https://bugs.documentfoundation.org/show_bug.cgi?id=155337 --- Comment #6 from Julien Nabet --- (In reply to BrendaEM from comment #5) > Libreoffice hangs at the start too for nearly a minute. Can not this be > fixed? Argh, if possible providing a backtrace by following https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace may help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153074] In WRITER Mode - INSERT FIELD Icon - Select MORE FIELDS - Error GENERAL ERROR Window appears
https://bugs.documentfoundation.org/show_bug.cgi?id=153074 Julien Nabet changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEEDINFO|RESOLVED --- Comment #6 from Julien Nabet --- Great news! Let's put this one to WFM then. Of course, don't hesitate to reopen this tracker if you reproduce this. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156359] Mouse over on back ground window tool bar will bring that window to foreground
https://bugs.documentfoundation.org/show_bug.cgi?id=156359 --- Comment #2 from seinf...@jsli.org --- I am using 7.5.4.2 ... perhaps there is a keyboard shortcut with which I'm inadvertently turning on Direct Cursor, because it activated again today and I definitely did not knowingly turn it on. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77999] [META] Autosave/Autorecovery/Backup copy issues
https://bugs.documentfoundation.org/show_bug.cgi?id=77999 Bug 77999 depends on bug 149716, which changed state. Bug 149716 Summary: Content that was Cut is treated as deleted content by AutoRecovery https://bugs.documentfoundation.org/show_bug.cgi?id=149716 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149716] Content that was Cut is treated as deleted content by AutoRecovery
https://bugs.documentfoundation.org/show_bug.cgi?id=149716 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #10 from Justin L --- This is not a bug. What would happen if, after you cut the cells, that you saved the document and exited? The same thing would happen. AutoSave is nothing more than "10 minutes are up - let me save a recovery copy", and so is no different than if you do the same steps manually. And Emergency save is the same thing - "oh no, I'm crashing. Let me try to save a recovery copy first". You cannot expect clipboard (which is an OS thing) to be saved along with your LibreOffice document. While the crash certainly is a bug, the recovery process described here is NOTABUG. (LibreOffice cannot anticipate your preferred state of the document in order to prepare for a possible crash.) P.S. These config options required a restart of LibreOffice in order to take effect. Since 7.5 the user is warned about that. -- You are receiving this mail because: You are the assignee for the bug.
