[Libreoffice-bugs] [Bug 105035] FILEOPEN DOCX changed framePr: Two frames, anchored to the same paragraph, imported as a single frame (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=105035 --- Comment #14 from Commit Notification --- Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/cbdd54e41a78e6a567d7ff97935721b07461cce5 tdf#105035 writerfilter framePr: don't allow overlap in extreme case It will be available in 7.6.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 75853] EDITING: Wrong timestamp in a table with date and time (except 00:00:00) before 1899-12-30
https://bugs.documentfoundation.org/show_bug.cgi?id=75853 --- Comment #14 from Robert Großkopf --- Bug still exists with LO 7.5.2.2 on OpenSUSE 15.4 64bit rpm Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154781] Keyboard input un-does paste (if cell was previously empty)
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 --- Comment #3 from ady --- You described what actually happened. What was supposed to be the expected behavior after step 4 in your comment 0? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 --- Comment #15 from BogdanB --- Patrick, you can mark this bug as Assigned, Resolved, so on... As you consider the actual status of this bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154715] "Edit Fields" for cross-reference fields should open on the type, format, and selection of the inserted field
https://bugs.documentfoundation.org/show_bug.cgi?id=154715 --- Comment #4 from Buovjaga --- (In reply to Buovjaga from comment #1) > Bibisected with Linux 43max to 333282478a956709e648427b412d90f90fc1437b > Related: fdo#75307 use the unique auto help id to identify tabpages Just a note: I was looking at the type to be specific. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 --- Comment #14 from bz137...@halfpi.co.uk --- Tested: https://dev-builds.libreoffice.org/daily/master/MacOSX-x86_64@tb94-TDF/2023-04-13_04.17.00/LibreOfficeDev_7.6.0.0.alpha0_MacOS_x86-64_sdk.dmg Could not find fault. Thanks for your work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154709] After saving as CSV (proceeding past the warning), there is no warning on close that unpreservable formatting or additional worskheets will be lost.
https://bugs.documentfoundation.org/show_bug.cgi?id=154709 Ramon Rakow changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Version|unspecified |7.4.2.3 release Resolution|WONTFIX |--- --- Comment #3 from Ramon Rakow --- So you think that it's acceptable that someone can: 1. Open a CSV 2. Make a change e.g. highlighting 3. Save -- read the warning that says that some formatting may be lost by continuing to save in csv, save anyway 4. Notice that none of their highlighting appears to have been lost by saving 5. Proceed to work on the file for hours 6. Save again and close 7. Come back the next day, all of that work is gone Or in a different scenario: 1. Open a CSV 2. Make some changes that are preserved by the CSV format 3. Save -- proceeding past the warning 4. Pass the station to wife / coworker / boss, who makes a bunch of changes that are not preserved by the CSV format, who then saves and closes the file, losing all their work and blaming you and libreoffice If you want to avoid too many nag popups, there is an easy solution here. When the editor window, which is currently displaying data that is not saved to the file (be it highlighting, conditional formatting, whatever) is closed-- that is when a warning is most pertinent. Because that is the point where work is irretrievably lost. It is not a nag to receive one extra warning when you attempt to close the window. If there is unsaved work, you already receive a warning-- if you have last saved to a file format that doesn't preserve the features libreoffice is displaying, that is another kind of unsaved work! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139112] Accessibility options dialog should adapt its width to long labels
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 --- Comment #29 from BogdanB --- (In reply to Buovjaga from comment #28) > (In reply to BogdanB from comment #27) > > (In reply to Buovjaga from comment #17) > > Do you now if this properties is what is needed? > > True > > > > If yes, I could do the change. > > If you can build on Windows and test with Polish, you can see what happens. I build on Linux (I didn't read your comment carefully) and there is no such a line. But I found on other similar settings with long text this property that can do this job: True -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106676] Decroise Unpivot Extension Basic Syntax Error in 5.3. Integration desired
https://bugs.documentfoundation.org/show_bug.cgi?id=106676 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #6 from BogdanB --- Is this bug NOT OUR BUG? Is this bug meanwhile solved? Brant, can you check again? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103381 BogdanB changed: What|Removed |Added Depends on||140027 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=140027 [Bug 140027] EDITING inserting rows before pivot table in row 1 copies format and images from headings -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140027] EDITING inserting rows before pivot table in row 1 copies format and images from headings
https://bugs.documentfoundation.org/show_bug.cgi?id=140027 BogdanB changed: What|Removed |Added Blocks||103381 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103381 [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103381 BogdanB changed: What|Removed |Added Depends on||153930 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153930 [Bug 153930] Pivot Table options discoverability -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153930] Pivot Table options discoverability
https://bugs.documentfoundation.org/show_bug.cgi?id=153930 BogdanB changed: What|Removed |Added Blocks||103381 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103381 [Bug 103381] [META] Pivot table (aka Data Pilot) bugs and enhancements -- 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 BogdanB changed: What|Removed |Added Depends on||134454 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=134454 [Bug 134454] Font not rendering properly when color is changed on mark glyph -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134454] Font not rendering properly when color is changed on mark glyph
https://bugs.documentfoundation.org/show_bug.cgi?id=134454 BogdanB changed: What|Removed |Added Blocks||71732 CC||buzea.bog...@libreoffice.or ||g Summary|Font not rendering properly |Font not rendering properly |when color is changed on|when color is changed on |mark glyph. |mark glyph 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 108576] [META] Writer page style bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108576 BogdanB changed: What|Removed |Added Depends on||154548 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154548 [Bug 154548] User defined page style disappears when exporting to docx/xlsx, closing and reopening -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154548] User defined page style disappears when exporting to docx/xlsx, closing and reopening
https://bugs.documentfoundation.org/show_bug.cgi?id=154548 BogdanB changed: What|Removed |Added Blocks||108576 Component|LibreOffice |Writer CC||buzea.bog...@libreoffice.or ||g --- Comment #7 from BogdanB --- Steps: - Open the document form comment 6. Go to Sidebar - Styles - Page Styles - apply "Used Page style" OR "New Page style". Everything OK. - Save as .docx. The page styles above have gone Tested with Version: 7.5.0.1.0+ (X86_64) / LibreOffice Community Build ID: f29b2b5b7a86fa813ec0410f2788cd9580c7e0b2 CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108576 [Bug 108576] [META] Writer page style bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146789] Inaccurate documentation of Writer Keyboard shortcuts
https://bugs.documentfoundation.org/show_bug.cgi?id=146789 BogdanB changed: What|Removed |Added Blocks||98290 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98290 [Bug 98290] [META] Better shortcuts on macOS -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98290] [META] Better shortcuts on macOS
https://bugs.documentfoundation.org/show_bug.cgi?id=98290 BogdanB changed: What|Removed |Added Depends on||146789 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146789 [Bug 146789] Inaccurate documentation of Writer Keyboard shortcuts -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 BogdanB changed: What|Removed |Added Depends on||153374 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153374 [Bug 153374] Hang using Keyboard viewer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 BogdanB changed: What|Removed |Added Blocks||136524 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136524 [Bug 136524] [META] Performance/hang/lag/high CPU issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103100] [META] Writer table bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103100 BogdanB changed: What|Removed |Added Depends on||154775 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154775 [Bug 154775] Part of document missing when opened from an email -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154775] Part of document missing when opened from an email
https://bugs.documentfoundation.org/show_bug.cgi?id=154775 BogdanB changed: What|Removed |Added Component|LibreOffice |Writer CC||buzea.bog...@libreoffice.or ||g Blocks||103100 OS|macOS (All) |All --- Comment #3 from BogdanB --- Also in Version: 7.5.0.1.0+ (X86_64) / LibreOffice Community Build ID: f29b2b5b7a86fa813ec0410f2788cd9580c7e0b2 CPU threads: 4; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103100 [Bug 103100] [META] Writer table bugs -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141093] Anchor "to paragraph" or 'to character' puts an image larger than page margin above present text (should be below)
https://bugs.documentfoundation.org/show_bug.cgi?id=141093 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||87740 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87740 [Bug 87740] [META] Anchor and text wrapping bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 BogdanB changed: What|Removed |Added Depends on||141093 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141093 [Bug 141093] Anchor "to paragraph" or 'to character' puts an image larger than page margin above present text (should be below) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 BogdanB changed: What|Removed |Added Depends on||141640 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=141640 [Bug 141640] Show value for line length > 100mm in writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 141640] Show value for line length > 100mm in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=141640 BogdanB changed: What|Removed |Added Blocks||87740 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=87740 [Bug 87740] [META] Anchor and text wrapping bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154762] Most current update 7.5.2.2 does not "read" EXEC files; previous version read and allowed me to save
https://bugs.documentfoundation.org/show_bug.cgi?id=154762 --- Comment #11 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154460] Unclear sentence: "Change typewriter apostrophe, single quotation marks and correct double primes."
https://bugs.documentfoundation.org/show_bug.cgi?id=154460 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 154436] Drag the outer circle in the circle diagram at Libre office impress-text is going outside of the circle
https://bugs.documentfoundation.org/show_bug.cgi?id=154436 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 154439] Text overflow when writing content in Diagrams, shapes and Symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=154439 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 40176] Show special paste options when needed
https://bugs.documentfoundation.org/show_bug.cgi?id=40176 --- Comment #30 from QA Administrators --- Dear mrkazoodle, 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 108479] [META] Paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108479 Bug 108479 depends on bug 40176, which changed state. Bug 40176 Summary: Show special paste options when needed https://bugs.documentfoundation.org/show_bug.cgi?id=40176 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150911] Copying png pictures to libre office presentaion (.odp) on Mac M1 Max makes crash
https://bugs.documentfoundation.org/show_bug.cgi?id=150911 --- Comment #4 from QA Administrators --- Dear Stefan Noll, 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 150400] File menu is missing some items
https://bugs.documentfoundation.org/show_bug.cgi?id=150400 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 150400] File menu is missing some items
https://bugs.documentfoundation.org/show_bug.cgi?id=150400 --- Comment #10 from QA Administrators --- Dear tomsaine, 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 151531] Libre Office Draw
https://bugs.documentfoundation.org/show_bug.cgi?id=151531 --- Comment #2 from QA Administrators --- Dear garystan1952, 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 93357] Thumbnail of ODP or PPTX presentation is updated to the last slide/page viewed
https://bugs.documentfoundation.org/show_bug.cgi?id=93357 --- Comment #19 from QA Administrators --- Dear Pedro, 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 75853] EDITING: Wrong timestamp in a table with date and time (except 00:00:00) before 1899-12-30
https://bugs.documentfoundation.org/show_bug.cgi?id=75853 --- Comment #13 from QA Administrators --- Dear Robert Großkopf, 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 44931] EDITING, FILEOPEN: cross-referencing HEADINGS in a sub-document from master-document fails
https://bugs.documentfoundation.org/show_bug.cgi?id=44931 --- Comment #12 from QA Administrators --- Dear gui, 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 77388] Images, inserted in a table cell, go out of cell borders when the document (and thus the table) is zoomed.
https://bugs.documentfoundation.org/show_bug.cgi?id=77388 --- Comment #12 from QA Administrators --- Dear Alex, 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 141093] Anchor "to paragraph" or 'to character' puts an image larger than page margin above present text (should be below)
https://bugs.documentfoundation.org/show_bug.cgi?id=141093 --- Comment #5 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 141640] Show value for line length > 100mm in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=141640 --- Comment #3 from QA Administrators --- Dear Ralf Rottschaefer, 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 118171] Complex symbols with wrong position after copy / paste
https://bugs.documentfoundation.org/show_bug.cgi?id=118171 --- Comment #7 from QA Administrators --- Dear Rainer Bielefeld Retired, 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 126892] visibility of cut/pasted section cannot be programmatically changed
https://bugs.documentfoundation.org/show_bug.cgi?id=126892 --- Comment #4 from QA Administrators --- Dear Lionel Elie Mamane, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://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 154783] PDF:
https://bugs.documentfoundation.org/show_bug.cgi?id=154783 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please take a look if opening, selecting pdf on the last position of writer files, that open the file in writer instead draw is what you need. The import is like in draw but in a writer file. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154733] Enhancement: Consistent behavior for change of zoom factor when using various plus and minus icons
https://bugs.documentfoundation.org/show_bug.cgi?id=154733 --- Comment #4 from Jim Raykowski --- (In reply to V Stuart Foote from comment #3) > I think approach of https://gerrit.libreoffice.org/c/core/+/146825 for bug > 45705 gets us partway in master against 7.6 Yes, this approach can be applied to the remaining places. Here is a list of what is done and what needs to be done: done by Rafael - https://gerrit.libreoffice.org/c/core/+/146825 basctl/source/basicide/basides1.cxx void Shell::ExecuteGlobal( SfxRequest& rReq ) needs patched sc/source/ui/view/prevwsh.cxx void ScPreviewShell::Execute( SfxRequest& rReq ) done by me - https://gerrit.libreoffice.org/c/core/+/104196 sc/source/ui/view/tabvwsh3.cxx void ScTabViewShell::Execute( SfxRequest& rReq ) done by Rafael - https://gerrit.libreoffice.org/c/core/+/146825 sd/source/ui/view/drviewse.cxx void DrawViewShell::FuSupport(SfxRequest& rReq) needs patched sd/source/ui/view/outlnvs2.cxx void OutlineViewShell::FuTemporary(SfxRequest &rReq) needs patched sw/source/uibase/uiview/pview.cxx void SwPagePreview::Execute( SfxRequest &rReq ) done by me - https://gerrit.libreoffice.org/c/core/+/102830 sw/source/uibase/uiview/view2.cxx void SwView::Execute(SfxRequest &rReq) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154775] Part of document missing when opened from an email
https://bugs.documentfoundation.org/show_bug.cgi?id=154775 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #2 from m.a.riosv --- Reproducible Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f22f7159ec1bd28d19f4a8b431893436419ecd64 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo Going to any cell in the second table, and with Menu/Table/Select/Table, shows as if the table is on the second page somewhere on the right hand side of the page. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 --- Comment #52 from Jake Doyle --- Protect your concrete surfaces from wear and tear with our expert concrete sealing services in Melbourne. At Premium Concrete Resurfacing, we use high-quality sealants to protect your concrete floors from water, stains, and other forms of damage. Our experienced team ensures a seamless and long-lasting finish, leaving your concrete surfaces looking great for years to come. Contact us today to learn more about how we can help you protect your concrete surfaces. Visit: - https://premiumconcreteresurfacing.com.au/concrete-sealing-melbourne -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154750] cell condition interacts with different columns and rows
https://bugs.documentfoundation.org/show_bug.cgi?id=154750 --- Comment #9 from m.a.riosv --- Please attach an example reduced as much as possible, and detail the steps to reproduce the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154630] If Selection is ticked in file naming dialog reached through File - Export, it should also be ticked in the subsequently opened PDF export settings dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=154630 --- Comment #13 from m.a.riosv --- What I have done time ago, it's customizing the toolbar as what's suggested in previous comment. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154750] cell condition interacts with different columns and rows
https://bugs.documentfoundation.org/show_bug.cgi?id=154750 --- Comment #8 from Darrell O'Brien --- I print out the pages from fixture sheet and supply it to people who do the tipping then they cut off each week and return section with their tips I then enter the teams number for program to lookup team name selected by the people tipping in sheet enter tips and use the condition to check input is referenced to Fixture sheet sme times cell doe's not show colour and I have to check condition programing and re program conditioning and on completing conditioning program a different cell in a previous weeks entry will go no colour so I have tried to check condition program of cell that change and have seen that the cell reference has changed so I reprogram cell that was changed and find that the data entered cell changes to no colour. Then I give up. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154750] cell condition interacts with different columns and rows
https://bugs.documentfoundation.org/show_bug.cgi?id=154750 --- Comment #7 from Darrell O'Brien --- I have tried to delete conditioning of enter tips cell and then condition enter tips cell selecting the box alongside equal to and going to Fixture sheet and set the reference cell under condition 1 then add a condition 2 and condition the second option then press ok. sometimes it repairs and other times it doe's not and I give up and contact you. computer keeps changing cell condition reference in enter tips sheet. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 Commit Notification changed: What|Removed |Added Whiteboard||target:7.6.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151194] VIEWING: Cannot maximize LO main window with low resolution screen in Arch XFCE with certain themes + language packs
https://bugs.documentfoundation.org/show_bug.cgi?id=151194 --- Comment #13 from flklb-b...@t-online.de --- Update: The bug is still present for me in version 7.4.6.2. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154783] New: PDF:
https://bugs.documentfoundation.org/show_bug.cgi?id=154783 Bug ID: 154783 Summary: PDF: Product: LibreOffice Version: 7.4.5.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: geoff.rushwo...@gmail.com As a user, I would like to be able to convert a PDF into a Writer document to be able to edit/annotate without having to use other converters. My attempt to open a document created a Draw document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139007] [META] PDF accessibility
https://bugs.documentfoundation.org/show_bug.cgi?id=139007 Bug 139007 depends on bug 152233, which changed state. Bug 152233 Summary: FILESAVE PDF PAC tool reports "Text object not tagged" error with signature line https://bugs.documentfoundation.org/show_bug.cgi?id=152233 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152233] FILESAVE PDF PAC tool reports "Text object not tagged" error with signature line
https://bugs.documentfoundation.org/show_bug.cgi?id=152233 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #4 from Gabor Kelemen (allotropia) --- I can no longer reproduce the error message of this one with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fc6806c4be8585ce0d35a6b581bf8b3dbf858500 CPU threads: 14; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: threaded and uploading to VeraPDF or checking with PAC tool locally. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134815] Add keyboard shorcuts for greek characters.
https://bugs.documentfoundation.org/show_bug.cgi?id=134815 V Stuart Foote changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED CC||vsfo...@libreoffice.org --- Comment #2 from V Stuart Foote --- Setting => WF, no sense that this is would ever be worked up if Dante is not going to tackle it for his own interest. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 Bug 98259 depends on bug 134815, which changed state. Bug 134815 Summary: Add keyboard shorcuts for greek characters. https://bugs.documentfoundation.org/show_bug.cgi?id=134815 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153935] PDF/UA: Mark heading rows of tables with autoformat in PDF export
https://bugs.documentfoundation.org/show_bug.cgi?id=153935 --- Comment #6 from Gabor Kelemen (allotropia) --- Checked in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fc6806c4be8585ce0d35a6b581bf8b3dbf858500 CPU threads: 14; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: threaded Now the PAC tool reports all cells in the first row are marked as TH. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154782] A11Y sidebar: scrolling no longer works with mouse wheel
https://bugs.documentfoundation.org/show_bug.cgi?id=154782 Gabor Kelemen (allotropia) changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |samuel.mehrbrodt@allotropia |desktop.org |.de CC||samuel.mehrbrodt@allotropia ||.de Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154782] New: A11Y sidebar: scrolling no longer works with mouse wheel
https://bugs.documentfoundation.org/show_bug.cgi?id=154782 Bug ID: 154782 Summary: A11Y sidebar: scrolling no longer works with mouse wheel Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kelem...@ubuntu.com Blocks: 103440, 142978 This is related to bug 148776 1. Open attachment 185791 then look at the new Accessibility sidebar, listing a lot of issues. 2. Try to scroll the list with the mouse wheel -> There is only about 1 line up/down movement. You need to use the vertical scroll bar to see the bottom of the list. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fc6806c4be8585ce0d35a6b581bf8b3dbf858500 CPU threads: 14; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: threaded Seems to work fine under GTK3 vcl. Likely a side effect from the dialog->sidebar conversion in bug 142978. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103440 [Bug 103440] [META] Sidebar accessibility bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=142978 [Bug 142978] Add an Accessibility sidebar -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103440] [META] Sidebar accessibility bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103440 Gabor Kelemen (allotropia) changed: What|Removed |Added Depends on||154782 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154782 [Bug 154782] A11Y sidebar: scrolling no longer works with mouse wheel -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154781] Keyboard input un-does paste (if cell was previously empty)
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 Jim Avera changed: What|Removed |Added Summary|Keyboard input un-does |Keyboard input un-does |paste from X PRIMARY|paste (if cell was |selection (if cell was |previously empty) |previously empty) | --- Comment #2 from Jim Avera --- The same problem happens with Control-V paste from the clipboard, so not specifically related to the X "PRIMARY" selection buffer. Sorry about the unnecessary complication. I changed the title to just say "paste". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154781] Keyboard input un-does paste from X PRIMARY selection (if cell was previously empty)
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 --- Comment #1 from Jim Avera --- I tried under Wayland (at least I think it was...) and the problem is the same. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154781] New: Keyboard input un-does paste from X PRIMARY selection (if cell was previously empty)
https://bugs.documentfoundation.org/show_bug.cgi?id=154781 Bug ID: 154781 Summary: Keyboard input un-does paste from X PRIMARY selection (if cell was previously empty) Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com STEPS TO REPRODUCE: 0. In Xorg (don't know about Wayland)... 1. Create or open a calc spreadsheet 2. In a terminal (e.g. gnome-terminal) select some text with the mouse 3. Click in an empty spreadsheet cell and middle-click (selected text appears the spreadsheet cell as expected) 4. Type any key on the keyboard RESULTS: The pasted text vanishes from the cell This happens only if the middle-click paste is the first thing entered; subsequent middle-click-pasted content is not erased by typing in that cell. The problem re-appears when starting in a new empty cell, or the same cell after deleting existing content. Note: Middle-click in the X Window system (or equivalent keyboard shortcut, if enabled), pastes the "PRIMARY selection" which is whatever is currently selected by the mouse in any window. It is independent of the "clipboard" used by Ctl-C/Ctl-V. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 16a35542aa07ed69c6c699d1c17f076d87708958 CPU threads: 12; 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 154780] Multiple spaces are reduced to one in the Writer result of a Base report
https://bugs.documentfoundation.org/show_bug.cgi?id=154780 mc...@sfr.fr changed: What|Removed |Added CC||mc...@sfr.fr --- Comment #1 from mc...@sfr.fr --- Created attachment 186632 --> https://bugs.documentfoundation.org/attachment.cgi?id=186632&action=edit Base with memo and report fields. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154780] New: Multiple spaces are reduced to one in the Writer result of a Base report
https://bugs.documentfoundation.org/show_bug.cgi?id=154780 Bug ID: 154780 Summary: Multiple spaces are reduced to one in the Writer result of a Base report Product: LibreOffice Version: unspecified Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mc...@sfr.fr Description: In database, the text of a "Memo" type field can look like this: Multiple spaces between words: Word1 Word2 Text OkOk The problem, when the report is generated, the multiple spaces are reduced to one and the presentation on Writer is not the same anymore: Multiple spaces between words: Word1 Word2 Text Ok Ok Steps to Reproduce: 1.In a 'Memo' type field, enter a text with multiple spaces between the words. 2. Make a report including this 'Memo' field 3.Run the report. Actual Results: Multiple spaces between words: Word1 Word2 Text Ok Ok Expected Results: Multiple spaces between words: Word1 Word2 Text OkOk Reproducible: Always User Profile Reset: No Additional Info: The same thing happens when importing into Base (via Calc) an access database with memo fields containing multiple spaces. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 --- Comment #12 from Patrick Luby --- (In reply to Buovjaga from comment #11) > Thanks a lot. As the steps did not mention using Math, I thought the > bibisect result was bogus. Maybe it is indirectly related, who knows? What I found was that when doing the steps in comment 10 was the only time that the catch block code was invoked in the accessibility code. The catch block is where I saw a release call on an autoreleased NSArray (the attributeNames variable was created with [NSMutableArray arrayWithObjects:], not [[NSMutableArray alloc] init:]): https://gerrit.libreoffice.org/c/core/+/150307/1/vcl/osx/a11ywrapper.mm Anyway, I'll commit the above patch if it passes gerrit's tests. I am not sure that the patch will fix this bug (I cannot reproduce the bug in my development build). So, if the bug still occurs in the next nightly build, can you take a sample in the Activity Monitor application when the Recover Document dialog appears? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 92688] When inserting a cross-reference, remember last used format in "reference to" for each type
https://bugs.documentfoundation.org/show_bug.cgi?id=92688 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4715 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154715] "Edit Fields" for cross-reference fields should open on the type, format, and selection of the inserted field
https://bugs.documentfoundation.org/show_bug.cgi?id=154715 sdc.bla...@youmail.dk changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=92 ||688 --- Comment #3 from sdc.bla...@youmail.dk --- Adding mention of enhancement request - bug 92688 (to remember the last used cross-reference type for "insert - field") -- in case it involves the same underlying code. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150734] Filter to exclude empty cells on Pivot Table still shows empty cells when deselected
https://bugs.documentfoundation.org/show_bug.cgi?id=150734 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 Buovjaga changed: What|Removed |Added Component|Calc|Formula Editor -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 Buovjaga changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #11 from Buovjaga --- Thanks a lot. As the steps did not mention using Math, I thought the bibisect result was bogus. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 139112] Accessibility options dialog should adapt its width to long labels
https://bugs.documentfoundation.org/show_bug.cgi?id=139112 --- Comment #28 from Buovjaga --- (In reply to BogdanB from comment #27) > (In reply to Buovjaga from comment #17) > Do you now if this properties is what is needed? > True > > If yes, I could do the change. If you can build on Windows and test with Polish, you can see what happens. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150734] Filter to exclude empty cells on Pivot Table still shows empty cells when deselected
https://bugs.documentfoundation.org/show_bug.cgi?id=150734 --- Comment #5 from lucky --- Hello Colin, Thank you for reporting the bug. I can confirm that the bug is present in master. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d9031bd83ffe718a80da9ecbdbeb485e35fbabee CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; 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 154687] Default attributes being overridden with no way to reset
https://bugs.documentfoundation.org/show_bug.cgi?id=154687 --- Comment #4 from Don Matschull --- (In reply to Buovjaga from comment #3) > (In reply to Don Matschull from comment #2) > > I understand that the Line Color setting is direct formatting that is taking > > precedence over the default style. I'd like a way to remove this direct > > formatting after it has once been set in order to return to the default > > style setting. > > Hit Ctrl-M or Format - Clear Direct Formatting Using (In reply to Buovjaga from comment #3) > (In reply to Don Matschull from comment #2) > > I understand that the Line Color setting is direct formatting that is taking > > precedence over the default style. I'd like a way to remove this direct > > formatting after it has once been set in order to return to the default > > style setting. > > Hit Ctrl-M or Format - Clear Direct Formatting Format>Clear Direct Formatting clears direct formatting applied to an object at the time. However, it does not clear any "globalized" direct formatting in the Line and Filling toolbar. I'm trying to find a way to change the Line Color setting in the Line and Filling toolbar so that any new object using the setting in the Default Style.(In reply to Buovjaga from comment #3) > (In reply to Don Matschull from comment #2) > > I understand that the Line Color setting is direct formatting that is taking > > precedence over the default style. I'd like a way to remove this direct > > formatting after it has once been set in order to return to the default > > style setting. > > Hit Ctrl-M or Format - Clear Direct Formatting If an object is selected, Format>Clear Direct Formatting clears any direct formatting set for that object. However, it does not reset the Line Color setting in the Line and Toolbar back to the default setting. Any new object draw will still not use the default setting. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107742] [META] Form control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107742 BogdanB changed: What|Removed |Added Depends on||146925 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146925 [Bug 146925] How to use form controls by keyboard only? Description is missing -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146925] How to use form controls by keyboard only? Description is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=146925 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||107742 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107742 [Bug 107742] [META] Form control bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 BogdanB changed: What|Removed |Added Depends on||134815 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=134815 [Bug 134815] Add keyboard shorcuts for greek characters. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134815] Add keyboard shorcuts for greek characters.
https://bugs.documentfoundation.org/show_bug.cgi?id=134815 BogdanB changed: What|Removed |Added Blocks||98259 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 39750] [META] General Math formula editor improvements
https://bugs.documentfoundation.org/show_bug.cgi?id=39750 BogdanB changed: What|Removed |Added Depends on||134861 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=134861 [Bug 134861] Drag-n-drop does not update the rendered formula until a key is pressed on keyboard -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 134861] Drag-n-drop does not update the rendered formula until a key is pressed on keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=134861 BogdanB changed: What|Removed |Added Blocks||39750 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=39750 [Bug 39750] [META] General Math formula editor improvements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114005] [META] Gradient fill bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114005 BogdanB changed: What|Removed |Added Depends on||150894 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150894 [Bug 150894] Added Gradients Not Saved in documents (ODT, ODG) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150894] Added Gradients Not Saved in documents (ODT, ODG)
https://bugs.documentfoundation.org/show_bug.cgi?id=150894 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||114005 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114005 [Bug 114005] [META] Gradient fill bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114005] [META] Gradient fill bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114005 BogdanB changed: What|Removed |Added Depends on||152536 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152536 [Bug 152536] FILEOPEN DOCX gradient page background is imported as solid -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152536] FILEOPEN DOCX gradient page background is imported as solid
https://bugs.documentfoundation.org/show_bug.cgi?id=152536 BogdanB changed: What|Removed |Added Blocks||114005 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114005 [Bug 114005] [META] Gradient fill bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114005] [META] Gradient fill bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114005 BogdanB changed: What|Removed |Added Depends on||145130 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=145130 [Bug 145130] Changing an LO Draw's background gradient color resets its gradient type, angle, and other properties -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145130] Changing an LO Draw's background gradient color resets its gradient type, angle, and other properties
https://bugs.documentfoundation.org/show_bug.cgi?id=145130 BogdanB changed: What|Removed |Added Blocks||114005 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114005 [Bug 114005] [META] Gradient fill bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 41560] [META] Keyboard shortcuts tab of Customization dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=41560 BogdanB changed: What|Removed |Added Depends on||151180 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=151180 [Bug 151180] Deleting keyboard shortcuts didn't work -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151180] Deleting keyboard shortcuts didn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=151180 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||41560 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=41560 [Bug 41560] [META] Keyboard shortcuts tab of Customization dialog -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 BogdanB changed: What|Removed |Added Depends on||150060 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150060 [Bug 150060] Keyboard Shortcuts for Black and White Screen don't work (Presentation Mode) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150060] Keyboard Shortcuts for Black and White Screen don't work (Presentation Mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=150060 BogdanB changed: What|Removed |Added Blocks||98259 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154762] Most current update 7.5.2.2 does not "read" EXEC files; previous version read and allowed me to save
https://bugs.documentfoundation.org/show_bug.cgi?id=154762 --- Comment #10 from Lysa --- Created attachment 186631 --> https://bugs.documentfoundation.org/attachment.cgi?id=186631&action=edit EXEC file example 2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154762] Most current update 7.5.2.2 does not "read" EXEC files; previous version read and allowed me to save
https://bugs.documentfoundation.org/show_bug.cgi?id=154762 --- Comment #9 from Lysa --- Created attachment 186630 --> https://bugs.documentfoundation.org/attachment.cgi?id=186630&action=edit EXEC file example 1 I've attached examples of EXEC files per your request. I have used LibreOffice for the last 5 years (at least!) to open this kind of file to view the contents. For example most of these files are from my father's old computer and he used ClarisWorks for almost everything; so I used LibreOffice to read them. This problem occurred after I updated my LibreOffice software earlier this week. Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 --- Comment #10 from Patrick Luby --- I can reproduce this in both LibreOffice 7.5.2.2 and the nightly build. Here are the steps that I did to reproduce the bug: 1. Open a new math formula document 2. Display the macOS Keyboard Viewer 3. Pu the cursor in the input area in the bottom half of the document 4. Input ASCII characters in Keyboard Viewer 5. Save the document using Command-S keys 6. Quit using Command-Q keys Sometimes it'll work, but sometimes the Recover Document dialog will appear during quitting. I took a sample in the Activity Monitor application when that dialog is display and no buttons are pressed in attachment 186629. In the sample, it looks like there is a crash in LibreOffice's accessibility code. Specifically, some memory is being deleted twice. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154772] Hairline and Very Thin borders are exported as dashed lines to Excel
https://bugs.documentfoundation.org/show_bug.cgi?id=154772 --- Comment #11 from Rafael Lima --- Fun fact... if you create a file in Excel and apply their "thin" border, and then export it to ODS using Excel, the border will open as a solid Hairline in Calc. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153374] Hang using Keyboard viewer
https://bugs.documentfoundation.org/show_bug.cgi?id=153374 --- Comment #9 from Patrick Luby --- Created attachment 186629 --> https://bugs.documentfoundation.org/attachment.cgi?id=186629&action=edit Sample when Recover Document dialog is displayed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149208] [XLSX] Excessive border weight in imported Excel files
https://bugs.documentfoundation.org/show_bug.cgi?id=149208 Rafael Lima changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4772 -- You are receiving this mail because: You are the assignee for the bug.
