[Libreoffice-bugs] [Bug 115698] fileopen fods a1 cell is black on lo viewer master daily build
https://bugs.documentfoundation.org/show_bug.cgi?id=115698 Michael Weghorn changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | --- Comment #8 from Michael Weghorn --- I'm currently looking into this. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129275] Typing problem with Old Hungarian text in Writer under Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=129275 --- Comment #8 from Kovács Viktor --- @Stuart MS' programs don't distinguish AltGr+any key with Alt+Ctrl+any key. Both works. It would be the keyword for resolving this problem. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129299] The default setting of the 'Change Anchor' can't be preset in the default template
https://bugs.documentfoundation.org/show_bug.cgi?id=129299 Dieter Praas changed: What|Removed |Added CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Blocks||103152 Severity|normal |enhancement --- Comment #2 from Dieter Praas --- As far as I know, the default anchor is "to character" (LO 6.5.0.0), while in LO 6.3.3 it is "to paragraph". I support the idea, to set the default anchor of images in the option dialog. But this is an enhancement. cc: Design-Team Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103152 [Bug 103152] [META] Writer image bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152 Dieter Praas changed: What|Removed |Added Depends on||129299 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129299 [Bug 129299] The default setting of the 'Change Anchor' can't be preset in the default template -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 113136] [META] Find & Replace Dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=113136 Dieter Praas changed: What|Removed |Added Depends on||129281 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129281 [Bug 129281] Find and Replace dialog: Replace shortcut (r) doesn't work; and no repeater function -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129281] Find and Replace dialog: Replace shortcut (r) doesn't work; and no repeater function
https://bugs.documentfoundation.org/show_bug.cgi?id=129281 Dieter Praas changed: What|Removed |Added Ever confirmed|0 |1 Version|6.2.8.2 release |Inherited From OOo Blocks||113136 Status|UNCONFIRMED |NEW --- Comment #2 from Dieter Praas --- (In reply to Durgapriyanka from comment #1) > Thank you for reporting the bug. I can reproduce in =>NEW Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113136 [Bug 113136] [META] Find & Replace Dialog -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128468] No ruler and therefore no easy way to add/edit/remove tab stops in writer on iOS
https://bugs.documentfoundation.org/show_bug.cgi?id=128468 --- Comment #13 from Commit Notification --- Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/online/commit/f1044b1daea45452e06e8b6213d6c53391253ded tdf#128468: Get rid of a bunch of pointless variables -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129291] Editing / Paste function
https://bugs.documentfoundation.org/show_bug.cgi?id=129291 Dieter Praas changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||dgp-m...@gmx.de --- Comment #1 from Dieter Praas --- (In reply to lda007 from comment #0) > I am using Libre Office (6.3.3.2 x86) Writter Portable and it doesn't seem > to allow me to paste from Microsoft Office 365 ProPlus. What do you mean with "doesn't seem to allow me"? Do you recieve an error message or simply nothing happens? Does paste from Microsoft Office 365 ProPlus work with other applications? => NEEDINFO -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128468] No ruler and therefore no easy way to add/edit/remove tab stops in writer on iOS
https://bugs.documentfoundation.org/show_bug.cgi?id=128468 --- Comment #12 from Commit Notification --- Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/online/commit/e8ee2aa06e654980248e0a7dbb599eb7738f8525 tdf#128468: Make the margin handles in the ruler work better in the iOS app -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 109527] [META] Spell check dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109527 Dieter Praas changed: What|Removed |Added Depends on||128123 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=128123 [Bug 128123] entire Writer App hangs up when spell checking runs and autosaving coincides with entering letters -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128074] SPELLCHECK: Writer freezes when trying to "Ignore All" in Spell Check when the flagged word is the next flagged word too.
https://bugs.documentfoundation.org/show_bug.cgi?id=128074 Dieter Praas changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8123 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128123] entire Writer App hangs up when spell checking runs and autosaving coincides with entering letters
https://bugs.documentfoundation.org/show_bug.cgi?id=128123 Dieter Praas changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8074 Blocks||109527 --- Comment #8 from Dieter Praas --- Sounds like a problem, that was reported in bug 128074. But it works in 6.3.3. HTK, so please test with a version 6.3.3 or newer if it will be available. => NEEDINFO Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109527 [Bug 109527] [META] Spell check dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114278] [META] Style filter drop down list in Styles deck of Sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=114278 Dieter Praas changed: What|Removed |Added Depends on||129298 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129298 [Bug 129298] Styles Lists should include Default -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129298] Styles Lists should include Default
https://bugs.documentfoundation.org/show_bug.cgi?id=129298 Dieter Praas changed: What|Removed |Added Keywords||needsUXEval Blocks||114278 CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Dieter Praas --- (In reply to DM from comment #0) > The simplest procedure would be just to include Default in the custom styles > list when Custom is chosen. Why don't you create a custom default style? > I think it would be of no > inconvenience to anyone to show it and of immense benefit. I think, there will be bug reports and discussion about it. Same, if it is part of applied styles, but not applied. So I won't support that idea, but let's ask and decide design-team. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=114278 [Bug 114278] [META] Style filter drop down list in Styles deck of Sidebar -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118988] Portrait/Landscape/Margins issue
https://bugs.documentfoundation.org/show_bug.cgi?id=118988 raal changed: What|Removed |Added URL|https://www.assistanceforal | |l.com/services/antivirus-su | |pport/malware-bytes-support | |/ | -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 112125] [META] Hyperlink dialog bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=112125 Dieter Praas changed: What|Removed |Added Depends on||129295 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129295 [Bug 129295] HYPERLINK DIALOG: Hyperlink Text below URL -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129295] HYPERLINK DIALOG: Hyperlink Text below URL
https://bugs.documentfoundation.org/show_bug.cgi?id=129295 Dieter Praas changed: What|Removed |Added Keywords||needsUXEval Summary|Hyperlink Text below URL|HYPERLINK DIALOG: Hyperlink ||Text below URL Blocks||112125 CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Dieter Praas --- (In reply to DM from comment #0) > Created attachment 156444 [details] > You now want to enter the 'Text' for the hyperlink, so the Text box should > be next under URL so you can just hit tab (to get to it) type your text and > hit Enter key to commit. If I hit tab, focus only changes between Help, Reset, Apply, OK and close. cc: Design-Tam for further input. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112125 [Bug 112125] [META] Hyperlink dialog bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129305] New: program gets hung up when attempting to save LibreOffice Calc spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=129305 Bug ID: 129305 Summary: program gets hung up when attempting to save LibreOffice Calc spreadsheet Product: LibreOffice Version: 6.3.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: i...@shorepl.com.au Description: After downloading latest update, whenever I use a spreadsheet which has been active for some time, the program shows "Not Responding" when I select Filesave. The save indicator bar on the bottom of the screen shows progress up to about 85 - 90% then stops and program hangs. Only way out is to close the program but when reopened, latest data input has not been saved. First time I've had this problem. Steps to Reproduce: 1.Open a Calc spreadsheet which was created under earlier version than 6.3.3.2 2.Update to version 6.3.3.2 3.Open same spreadsheet, input new data, attempt Filesave Actual Results: Program crashes as described above Expected Results: File should have been saved Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68695] EDITING: Comments cannot be resized while editing - missing squares around the comment/note
https://bugs.documentfoundation.org/show_bug.cgi?id=68695 --- Comment #42 from David --- Oops. Forgot to say my current test version/environment. Version: 6.3.3.2 (Win x64) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129304] New: Spacing above paragraph is different for the first column on a page compared to following columns when column breaks are used
https://bugs.documentfoundation.org/show_bug.cgi?id=129304 Bug ID: 129304 Summary: Spacing above paragraph is different for the first column on a page compared to following columns when column breaks are used Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Created attachment 156452 --> https://bugs.documentfoundation.org/attachment.cgi?id=156452=edit Two columns starting with headings Having a column break applied to a paragraph, its "spacing above" will be different on first column compared to following columns on the same page. The attachment contains a 2-columnar section with some text divided into two parts, each having own Heading 1. The Heading 1 style is modified to have section breaks before inserted automatically. The spacing above is the default 4.23 mm. The problem is that the headings are misaligned vertically on the first and second columns. They should be starting on the same position vertically, but on the second column, it seems, the spacing above is taken twice (modifying the style's spacing changes the spacing on the page for both headings simultaneously, but seemingly twice more for the second column). Tested with Version: 6.3.4.1 (x64) Build ID: a21169d87339dfa44546f33d6d159e89881e9d92 CPU threads: 12; OS: Windows 10.0; UI render: GL; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 --- Comment #50 from Heiko Tietze --- (In reply to mirko.pieropan from comment #48) > What happens if I do it using LO Impress > Version: 6.5.0.0.alpha0+ > > Tested on 6.2.6.2 as well. I run the test with Writer (cannot check now as the mac is not my primary system) so maybe it's an issue of Impress. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 --- Comment #49 from Heiko Tietze --- (In reply to mirko.pieropan from comment #45) > Version: 6.3.1.2 > ... > Doesn't work for me QA replied to me on IRC you should install a newer version (in particular the fresh releases may have glitches). If the issue persists please file a new ticket. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68695] EDITING: Comments cannot be resized while editing - missing squares around the comment/note
https://bugs.documentfoundation.org/show_bug.cgi?id=68695 --- Comment #41 from David --- Confirmed bug did NOT exist in version 3.3. Confirmed regression. I don't have a full VM environment setup so I'm not up to confirming the version marked is the first version with the regression. Regression tag already set. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118988] Portrait/Landscape/Margins issue
https://bugs.documentfoundation.org/show_bug.cgi?id=118988 Jackson Pole changed: What|Removed |Added URL||https://www.assistanceforal ||l.com/services/antivirus-su ||pport/malware-bytes-support ||/ -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68695] EDITING: Comments cannot be resized while editing - missing squares around the comment/note
https://bugs.documentfoundation.org/show_bug.cgi?id=68695 --- Comment #40 from David --- Confirmed present in current version. Testing 3.3 now and will update based on results. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70710] filled areas are not filled for WMF images
https://bugs.documentfoundation.org/show_bug.cgi?id=70710 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g --- Comment #11 from BogdanB --- The same in Version: 6.3.3.2 (x64). No fill. Build ID: a64200df03143b798afd1ec74a12ab50359878ed CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; Locale: ro-RO (ro_RO); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129254] when copy and pasting lots of text from a pdf writer freezes
https://bugs.documentfoundation.org/show_bug.cgi?id=129254 Elmar changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #5 from Elmar --- @Roman I have a large PDF and needed to copy many parts into a new document, resulting in many copies and pastes. After a number of instances of such select, copy, paste Writer froze (the period was less than 10mins- the interval between autosaves). Left it for a while but Writer did not unfreeeze, so had to cancel. After a second attempt, I opened up my document in v6.0 (the Repository version) and completed the exercise without incident - the copying and pasting from PDF to Writer took me more than an hour complete (large document). Hope that helps. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128468] No ruler and therefore no easy way to add/edit/remove tab stops in writer on iOS
https://bugs.documentfoundation.org/show_bug.cgi?id=128468 --- Comment #11 from Commit Notification --- Tor Lillqvist committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/online/commit/7585789456cc5e42d968a483d83cc6248b1f3862 tdf#128468: Make dragging the margins in the ruler work better in iOS app -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128671] master branch cannot be built without manual hacks with Aarch64 distro config
https://bugs.documentfoundation.org/show_bug.cgi?id=128671 --- Comment #16 from Mark --- Please fix this bug! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 88895] Rotated text (via Character or Paragraph Position) in table expands cell instead of flowing down
https://bugs.documentfoundation.org/show_bug.cgi?id=88895 --- Comment #11 from QA Administrators --- Dear Timur, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121074] Missing images in an XLSX on Linux and macOS (OK on Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=121074 --- Comment #10 from QA Administrators --- Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 125848] Text orientation from master does not properly apply to other pages
https://bugs.documentfoundation.org/show_bug.cgi?id=125848 --- Comment #3 from QA Administrators --- Dear jakelewis2010, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129283] Cells with conditional formatting are treat as protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=129283 --- Comment #5 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 123073] mail merge: conditional text followed by empty field not printed
https://bugs.documentfoundation.org/show_bug.cgi?id=123073 --- Comment #7 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 123073] mail merge: conditional text followed by empty field not printed
https://bugs.documentfoundation.org/show_bug.cgi?id=123073 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 mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94461] Predefined Templates and Template Folders are not Deletable in Template Manager
https://bugs.documentfoundation.org/show_bug.cgi?id=94461 --- Comment #13 from QA Administrators --- Dear Harald Koester, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 47612] Exported graphics from Writer to .doc not coming out correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=47612 --- Comment #9 from QA Administrators --- Dear skiani, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118256] PDF export of presentation with svg image with stroke-miterlimit is wrong.
https://bugs.documentfoundation.org/show_bug.cgi?id=118256 --- Comment #2 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 119871] New feature “spell out” numbering doesn't work on Linux (Vanilla)
https://bugs.documentfoundation.org/show_bug.cgi?id=119871 --- Comment #8 from QA Administrators --- Dear RGB, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120458] Some graphic objects in XLSX display incorrectly in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=120458 --- Comment #8 from QA Administrators --- Dear Daniel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120502] Assigns style to columns it cannot handle in .xlsx files
https://bugs.documentfoundation.org/show_bug.cgi?id=120502 --- Comment #3 from QA Administrators --- Dear Aidas Kasparas, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129283] Cells with conditional formatting are treat as protected cells
https://bugs.documentfoundation.org/show_bug.cgi?id=129283 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128999] EDITING:find replaces "\n" in document with newline formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=128999 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120103] Problem highlighting text in a comment box
https://bugs.documentfoundation.org/show_bug.cgi?id=120103 --- Comment #2 from QA Administrators --- Dear George, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 111340] cropped image aspect ratio (jpeg, eps, at least) fails on saving and re-opening .odp file and on export to PDF.
https://bugs.documentfoundation.org/show_bug.cgi?id=111340 --- Comment #5 from QA Administrators --- Dear Eric M, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 94109] Writer sluggish when writing text
https://bugs.documentfoundation.org/show_bug.cgi?id=94109 --- Comment #7 from QA Administrators --- Dear Karl, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 45089] FILELOAD: Table formatting damaged loading file from .doc
https://bugs.documentfoundation.org/show_bug.cgi?id=45089 --- Comment #14 from QA Administrators --- Dear soshial, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118887] CALC: Read Combo chart that has multiple series of data from XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=118887 --- Comment #5 from QA Administrators --- Dear Jonathan Bach, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120164] FILEOPEN XLSX Different font effects (Overlining, Strikethrough) in a cell
https://bugs.documentfoundation.org/show_bug.cgi?id=120164 --- Comment #3 from QA Administrators --- Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121690] Comments are not shown in position saved
https://bugs.documentfoundation.org/show_bug.cgi?id=121690 --- Comment #3 from QA Administrators --- Dear Eduardo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 81504] Roundtripping content in SDT block result in all data in same paragraph
https://bugs.documentfoundation.org/show_bug.cgi?id=81504 --- Comment #10 from QA Administrators --- Dear Jorendc, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121027] missing apostrophe in xlsx import
https://bugs.documentfoundation.org/show_bug.cgi?id=121027 --- Comment #3 from QA Administrators --- Dear Elie Roux, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68695] EDITING: Comments cannot be resized while editing - missing squares around the comment/note
https://bugs.documentfoundation.org/show_bug.cgi?id=68695 --- Comment #39 from QA Administrators --- Dear Peter Draganov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118616] PDF export of a form's scrollable memo field shows fewer lines than on the original form
https://bugs.documentfoundation.org/show_bug.cgi?id=118616 --- Comment #6 from QA Administrators --- Dear Alan Wheeler, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 121366] Export to PDF creates non-functional hyperlinks when used in frame attached to header/footer
https://bugs.documentfoundation.org/show_bug.cgi?id=121366 --- Comment #5 from QA Administrators --- Dear Alexander Graf, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118615] Base form text box content overflows in PDF exported without form support when viewed in Adobe Acrobat Reader
https://bugs.documentfoundation.org/show_bug.cgi?id=118615 --- Comment #7 from QA Administrators --- Dear Alan Wheeler, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 114067] Pressing CTRL + ENTER does not create pagebreak if chapter numbering is selected [EDITING]
https://bugs.documentfoundation.org/show_bug.cgi?id=114067 --- Comment #9 from QA Administrators --- Dear Clemens Prill, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118405] Export as PDF shows gaps in Greek words when using TexGyre fonts
https://bugs.documentfoundation.org/show_bug.cgi?id=118405 --- Comment #10 from QA Administrators --- Dear JesseSteele, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120522] FILEOPEN XLSX Wrapped text looks different in Excel and Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=120522 --- Comment #3 from QA Administrators --- Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 120523] FILEOPEN XLSX Text with a manual line break looks different in Excel and Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=120523 --- Comment #3 from QA Administrators --- Dear Gabor Kelemen, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118688] Filled form fields exported to PDF show as empty after converting to JPEG with ImageMagick
https://bugs.documentfoundation.org/show_bug.cgi?id=118688 --- Comment #8 from QA Administrators --- Dear Justin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 117638] FILEOPEN: Corrupt image when loading RTF file
https://bugs.documentfoundation.org/show_bug.cgi?id=117638 --- Comment #9 from QA Administrators --- Dear Milan Bouchet-Valat, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129303] EDITING:select all(with ctrl-A) then copy & paste does not preserve italic style near end of selection
https://bugs.documentfoundation.org/show_bug.cgi?id=129303 VincentYu changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #1 from VincentYu --- Only happens sometimes with complex documents, pasting across documents. Not reproducible with given steps. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129302] FORMATTING:chapter name field in header does not reflect first chapter in current page
https://bugs.documentfoundation.org/show_bug.cgi?id=129302 --- Comment #3 from VincentYu --- Version: 6.2.8.2 (x64) Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee CPU threads: 2; OS: Windows 6.3; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129303] New: EDITING:select all(with ctrl-A) then copy & paste does not preserve italic style near end of selection
https://bugs.documentfoundation.org/show_bug.cgi?id=129303 Bug ID: 129303 Summary: EDITING:select all(with ctrl-A) then copy & paste does not preserve italic style near end of selection Product: LibreOffice Version: 6.2.8.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vincent_hy...@hotmail.com Description: Italic style is not preserved with copy/paste operation, either from page to page within same document or to a different document. Steps to Reproduce: 1.create a 2 page document with texts, mixed with italic style on 1st page 2.on page 1, select all by pressing ctrl-a 3.copy & paste to page 2 Actual Results: some italic style is lost, becomes normal/regular style after paste Expected Results: all styles should be preserved when pasted. Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.8.2 (x64) Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee CPU threads: 2; OS: Windows 6.3; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129121] FILESAVE Bad Allocation crash (32bit build problem only)
https://bugs.documentfoundation.org/show_bug.cgi?id=129121 --- Comment #13 from MarvinWWW --- Aron: Thanks for your reply. I kind of THOUGHT there would be no fixed schedule. I figured I should ask, though, since this bug causes a crash and loss of data. I thought it might be assigned a higher priority. Oh, well. I went online and found two fabulous deals on refurbished 64-bit machines. One has an Intel I3 processor plus 4 GB of RAM. The other has an AMD processor plus 4 GB of RAM. I will try both. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129300] CALC: GUI: cell style settings from Alignment tab don't properly reflect in Organizer tab
https://bugs.documentfoundation.org/show_bug.cgi?id=129300 Mihkel Tõnnov changed: What|Removed |Added CC||caol...@redhat.com Keywords||bibisected, regression --- Comment #5 from Mihkel Tõnnov --- Bibisected using bibisect-linux-64-6.0. The first bad commit, 00657aef09d854c74fb426a935a3e8b1fc390bb0, is unfortunately the migration to Gettext: https://gerrit.libreoffice.org/plugins/gitiles/core/+/00657aef09d854c74fb426a935a3e8b1fc390bb0%5E!/ Adding its committer Caolán to Cc, in case he wants to take a look. Relevant items: RID_SVXITEMS_HORJUST_STANDARD ... RID_SVXITEMS_HORJUST_REPEAT RID_SVXITEMS_VERJUST_STANDARD ... RID_SVXITEMS_VERJUST_BOTTOM RID_SVXITEMS_JUSTMETHOD_AUTO and RID_SVXITEMS_JUSTMETHOD_DISTRIBUTE I am not a programmer, but comparing these with the settings from other, working tab pages, it seems like these is something amiss between include/editeng/editrids.hrc and editeng/source/items/justifyitem.cxx. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129302] FORMATTING:chapter name field in header does not reflect first chapter in current page
https://bugs.documentfoundation.org/show_bug.cgi?id=129302 --- Comment #2 from VincentYu --- On Writer 6.0 guide page 382: Note A cross-reference field in the header of a page picks up the first heading of that level on the page, and a field in the footer picks up the last heading of that level on the page. Writer 6.2.8.2 release behaves differently. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129302] FORMATTING:chapter name field in header does not reflect first chapter in current page
https://bugs.documentfoundation.org/show_bug.cgi?id=129302 --- Comment #1 from VincentYu --- Created attachment 156451 --> https://bugs.documentfoundation.org/attachment.cgi?id=156451=edit 3 pages with 1 heading1 and 2 heading2's and header -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129302] New: FORMATTING:chapter name field in header does not reflect first chapter in current page
https://bugs.documentfoundation.org/show_bug.cgi?id=129302 Bug ID: 129302 Summary: FORMATTING:chapter name field in header does not reflect first chapter in current page Product: LibreOffice Version: 6.2.8.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: vincent_hy...@hotmail.com Description: chapter name inserted into header should show first heading of that level on the page, instead it showed the previous one. Steps to Reproduce: 1.enter 3 lines of text 2.turn 2nd line into heading level 2 using styles->heading 2 3.add heading, insert->fields->more->document->chapter format->chapter name level->2 Actual Results: heading on previous page is shown Expected Results: should've shown the heading in current page Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 34959] Export/convert presentation to video
https://bugs.documentfoundation.org/show_bug.cgi?id=34959 --- Comment #18 from paulyste...@web.de --- workaround export slides as images with extension "export as image 0.9.3" than you can make a film with a simple film editor. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129301] New: Converting a Text field to a date, the field is of type date, but it's not valid due to a ' character at the beginning of the field . (extra ' character at the beg
https://bugs.documentfoundation.org/show_bug.cgi?id=129301 Bug ID: 129301 Summary: Converting a Text field to a date, the field is of type date, but it's not valid due to a ' character at the beginning of the field . (extra ' character at the beginning) Product: LibreOffice Version: 3.3.4 release Hardware: x86-64 (AMD64) OS: Mac OS X (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: t...@barfoots.ca Description: can NOT convert a Text field such as 09/28/2019 to a valid date type field. All attempts leave an additional character at the beginning of the converted field. example: 09/28/2019 converts to '09/28/2019 Mac OS Steps to Reproduce: 1. create a Text field containing 09/28/2019 2. Format this field to a date 3. Date field is not valid, contains extra character Actual Results: '09/28/2019 Expected Results: 09/28/2019 Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129286] Formatting one cell causes cells to its right to change
https://bugs.documentfoundation.org/show_bug.cgi?id=129286 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Resolution|--- |NOTABUG Status|NEEDINFO|RESOLVED --- Comment #3 from m.a.riosv --- If I'm not wrong it's only a matter of disable the option: Menu/Tools/Options/LibreOffice calc/General - Input settings - Expand formatting. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129300] CALC: GUI: cell style settings from Alignment tab don't properly reflect in Organizer tab
https://bugs.documentfoundation.org/show_bug.cgi?id=129300 --- Comment #4 from Mihkel Tõnnov --- Created attachment 156450 --> https://bugs.documentfoundation.org/attachment.cgi?id=156450=edit Cell style - Organizer tab (5.4.7) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129300] CALC: GUI: cell style settings from Alignment tab don't properly reflect in Organizer tab
https://bugs.documentfoundation.org/show_bug.cgi?id=129300 --- Comment #2 from Mihkel Tõnnov --- Created attachment 156448 --> https://bugs.documentfoundation.org/attachment.cgi?id=156448=edit Cell style - Organizer tab (6.4.0b1) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129300] CALC: GUI: cell style settings from Alignment tab don't properly reflect in Organizer tab
https://bugs.documentfoundation.org/show_bug.cgi?id=129300 --- Comment #3 from Mihkel Tõnnov --- Created attachment 156449 --> https://bugs.documentfoundation.org/attachment.cgi?id=156449=edit Cell style - Alignment tab (5.4.7) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129300] CALC: GUI: cell style settings from Alignment tab don't properly reflect in Organizer tab
https://bugs.documentfoundation.org/show_bug.cgi?id=129300 --- Comment #1 from Mihkel Tõnnov --- Created attachment 156447 --> https://bugs.documentfoundation.org/attachment.cgi?id=156447=edit Cell style - Alignment tab (6.4.0b1) -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129300] New: CALC: GUI: cell style settings from Alignment tab don't properly reflect in Organizer tab
https://bugs.documentfoundation.org/show_bug.cgi?id=129300
Bug ID: 129300
Summary: CALC: GUI: cell style settings from Alignment tab
don't properly reflect in Organizer tab
Product: LibreOffice
Version: Inherited From OOo
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Calc
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: mihh...@gmail.com
When modifying a cell style, the options set on Alignment tab don't get
properly reflected in Organizer tab - see attached screenshots.
There's different levels of breakage here. The first bit used to (mostly) work
before, but was broken somewhere between 5.4.7 and 6.0 (I'll try to bibisect
this later to find what broke them).
1) Horizontal/Vertical (under text alignment)
- Values in Organizer tab are always shown as untranslatable "Horizontal
alignment default" / "Vertical alignment default", no matter the actual
alignment setting in Alignment tab (for added strangeness, those strings are in
Weblate, however their key-IDs change depending on the actual value, and those
key-IDs in turn don't match any strings)
- A (translatable) "Automatic" is shown after them both, regardless of actual
settings (in 5.4.7, "Automatic" was shown for all horizontal/vertical alignment
settings except "Distributed")
- The setting "Distributed" (for both horizontal and vertical alignment) isn't
remembered after clicking OK in the dialog.
The rest was broken already in OOo 3.2, as confirmed with an old live CD.
2) Indent (under text alignment)
- No description
- Value shown as multiplied by 20 (and without unit)
- If value is changed back to 0 while the dialog is open, previous non-0 value
is shown
3) Rotation ("Degrees")
- No description
- Value shown as multiplied by 100 (and without degree mark)
- If value is changed back to 0 while the dialog is open, previous non-0 value
is shown
4) Reference edge
- Description shown as "..."
- Value shown as 0, 1 or 3
5) All the checkboxes
- No description
- Value shown as untranslatable "TRUE" or "FALSE" if toggled (depending on the
relevant setting in parent style)
- Value is not updated if the setting is changed again while the dialog is
open.
--
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129250] Manage changes dialog: (seemingly) useless clickable header for Action column
https://bugs.documentfoundation.org/show_bug.cgi?id=129250 raal changed: What|Removed |Added Keywords|bibisectRequest |bibisected, bisected CC||caol...@redhat.com, ||r...@post.cz OS|Windows (All) |All --- Comment #3 from raal --- This seems to have begun at the below commit. Adding Cc: to Caolán McNamara ; Could you possibly take a look at this one? Thanks 01cfa1522e70a467cd7157188de4dd8d9b809493 is the first bad commit commit 01cfa1522e70a467cd7157188de4dd8d9b809493 Author: Jenkins Build User Date: Sat Apr 27 13:53:31 2019 +0200 source sha:56dd851cfc77c362c3db5c0aae4a490c7f6782cc author Caolán McNamara 2019-04-18 16:49:26 +0100 committer Caolán McNamara 2019-04-27 12:41:14 +0200 commit 56dd851cfc77c362c3db5c0aae4a490c7f6782cc (patch) tree0f5f6564e0b9af8123f4cebfe9a2f55c1a57 parent 6afbe153ffd4cab27f0a7bb77f71f25923dc2e43 (diff) weld cluster of change tracking dialogs -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129299] The default setting of the 'Change Anchor' can't be preset in the default template
https://bugs.documentfoundation.org/show_bug.cgi?id=129299 --- Comment #1 from Stuart Halliday --- "Each time I have to then change the default setting of that image from 'Paragraph' to 'Page' as I find it's much easier to manipulate the text flow around the image and to allow the image to rest at top left of the page." to Each time I have to then change the default setting of the anchor of that image from 'Paragraph' to 'Page' as I find it's much easier to manipulate the text flow around the image and to allow the image to rest at top left of the page. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129299] New: The default setting of the 'Change Anchor' can't be preset in the default template
https://bugs.documentfoundation.org/show_bug.cgi?id=129299 Bug ID: 129299 Summary: The default setting of the 'Change Anchor' can't be preset in the default template Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stu...@stuarthalliday.com I always insert an image from the clipboard to Writer in my documents. Each time I have to then change the default setting of that image from 'Paragraph' to 'Page' as I find it's much easier to manipulate the text flow around the image and to allow the image to rest at top left of the page. Can we get a setting added in preferences to prefix this by default to Page? Each time I create a new document and drop an image into Writer, I've got to do this monotonous Anchor changes to set it to Page. It would be much easier on me if Writer could do this for me. I have to do this dozens of times! -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129298] New: Styles Lists should include Default
https://bugs.documentfoundation.org/show_bug.cgi?id=129298 Bug ID: 129298 Summary: Styles Lists should include Default Product: LibreOffice Version: 6.3.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: miscellane...@paintdrawer.co.uk Suggestion to include 'Default' in Custom Styles (& Applied Styles) In the styles sidebar you can choose Custom Styles. Generally this is the one I (and I am sure others) would want to be permanently up if you use styles. However, it needs to include the Default style as well, and because it doesn't you're constantly having to switch out of it just to use the default style, and then come back, which is a greatly annoying and regular procedure. The simplest procedure would be just to include Default in the custom styles list when Custom is chosen. In fact, you probably want Default on the Applied Styles too where it otherwise only seems to appear once applied. I think it would be of no inconvenience to anyone to show it and of immense benefit. Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129297] New: Menu "View > Show Ruler" doesn't work in a writer document using the Android app
https://bugs.documentfoundation.org/show_bug.cgi?id=129297 Bug ID: 129297 Summary: Menu "View > Show Ruler" doesn't work in a writer document using the Android app Product: LibreOffice Version: unspecified Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cont...@0x17.ch Description: Tapping on "View > Show Ruler" seems not to do anything using when editing a writer document using the Android app. Steps to Reproduce: 1. Create/open a writer document using the Android app 2. Tap on the hamburger icon 3. Tap on "View > Show Ruler" Actual Results: The ruler doesn't show up. Expected Results: The ruler should show up. Reproducible: Always User Profile Reset: No Additional Info: Tested using the build from 2019-12-06 on Android 8.1.8 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129296] Not possible to open password protected documents using the Android app
https://bugs.documentfoundation.org/show_bug.cgi?id=129296 --- Comment #2 from Nicolas Christener --- Created attachment 156446 --> https://bugs.documentfoundation.org/attachment.cgi?id=156446=edit An other test document, pass: RockyTheDog42 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129296] Not possible to open password protected documents using the Android app
https://bugs.documentfoundation.org/show_bug.cgi?id=129296 --- Comment #1 from Nicolas Christener --- Created attachment 156445 --> https://bugs.documentfoundation.org/attachment.cgi?id=156445=edit Test document, pass: RockyTheDog42 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129296] New: Not possible to open password protected documents using the Android app
https://bugs.documentfoundation.org/show_bug.cgi?id=129296 Bug ID: 129296 Summary: Not possible to open password protected documents using the Android app Product: LibreOffice Version: unspecified Hardware: ARM OS: Android Status: UNCONFIRMED Severity: normal Priority: medium Component: Android Editor Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cont...@0x17.ch Description: It seems that it's not possible, to open password protected document using the Android app. Steps to Reproduce: 1. Open a password protected file using the Android app Actual Results: It's not possible to open the file, after entering the password, only a gray document canvas shows up. Expected Results: The document should properly open. Reproducible: Always User Profile Reset: No Additional Info: Tested with the build from 2019-12-06 on Android 8.1.x -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129295] New: Hyperlink Text below URL
https://bugs.documentfoundation.org/show_bug.cgi?id=129295 Bug ID: 129295 Summary: Hyperlink Text below URL Product: LibreOffice Version: 6.3.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: miscellane...@paintdrawer.co.uk Created attachment 156444 --> https://bugs.documentfoundation.org/attachment.cgi?id=156444=edit Hyperlink Dialog Suggestion to put 'Text' box straight after 'URL' in Hyperlink. Usually in creating a hyperlink, one has the URL in the clipboard. So in LibreOffice one does Ctrl-K and up comes the hyperlink dialog, Ctrl-V pastes the URL. You now want to enter the 'Text' for the hyperlink, so the Text box should be next under URL so you can just hit tab (to get to it) type your text and hit Enter key to commit. Obviously for this logic, the Text entry box needs to be shifted up as the next entry box in tab order after URL, which is what I strongly recommend. Screenshot of dialog attached. d Version: 6.3.2.2 (x64) Build ID: 98b30e735bda24bc04ab42594c85f7fd8be07b9c CPU threads: 2; OS: Windows 10.0; UI render: default; VCL: win; Locale: en-GB (en_GB); UI-Language: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 --- Comment #48 from mirko.piero...@studenti.polito.it --- Created attachment 156443 --> https://bugs.documentfoundation.org/attachment.cgi?id=156443=edit screenshot showing the reported behaviour What happens if I do it using LO Impress Version: 6.5.0.0.alpha0+ Build ID: 5f40fa6f29a2a51a5f843f7a92d57721e1b8d540 CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; Locale: it-IT (it_IT.UTF-8); UI-Language: en-US Calc: threaded Tested on 6.2.6.2 as well. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 --- Comment #47 from mirko.piero...@studenti.polito.it --- Created attachment 156442 --> https://bugs.documentfoundation.org/attachment.cgi?id=156442=edit an image to put in the ellipse Could you see if you can put the attached jpg image in the ellipse by reproducing the steps in comment #34? -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 --- Comment #46 from mirko.piero...@studenti.polito.it --- Created attachment 156441 --> https://bugs.documentfoundation.org/attachment.cgi?id=156441=edit just a slide with an ellipse -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129279] duplicate bibliography entries if mentioned multiple times in document
https://bugs.documentfoundation.org/show_bug.cgi?id=129279 --- Comment #4 from Andrea --- clarification: * I do not access the bibliography database itself * I do not try to change bibliography database entries * I simply "use" the bibliography to add biblio-references in a writer document * if the same reference is used multiple times in the document, I am expecting the biblio-directory at the end of the document to list each biblio-entry only once -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129279] duplicate bibliography entries if mentioned multiple times in document
https://bugs.documentfoundation.org/show_bug.cgi?id=129279 --- Comment #3 from Andrea --- 6.4.0.0.beta1 includes the bug Version: 6.4.0.0.beta1 (x64) Build-ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107739] [META] Field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107739 Dieter Praas changed: What|Removed |Added Depends on|30873 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=30873 [Bug 30873] Field variables break with additional formats -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129294] [META] Variable field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=129294 Dieter Praas changed: What|Removed |Added Depends on||30873 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=30873 [Bug 30873] Field variables break with additional formats -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129202] Alignment inside Text Box Crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=129202 --- Comment #3 from Xisco Faulí --- (In reply to Telesto from comment #2) > @Xisco > Slightly off topic: I get a crash when following the steps with skia enabled > (forced mode) If you can reproduce it when skia is enabled and you can't when it's not, then fill a new bug for skia only. Thanks in advance -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 30873] Field variables break with additional formats
https://bugs.documentfoundation.org/show_bug.cgi?id=30873 Dieter Praas changed: What|Removed |Added Blocks|107739 |129294 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107739 [Bug 107739] [META] Field bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=129294 [Bug 129294] [META] Variable field bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129294] [META] Variable field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=129294 Dieter Praas changed: What|Removed |Added Depends on||62594 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=62594 [Bug 62594] writer: invisible input field for defined variable is not possible -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 107739] [META] Field bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107739 Dieter Praas changed: What|Removed |Added Depends on|62594 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=62594 [Bug 62594] writer: invisible input field for defined variable is not possible -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 62594] writer: invisible input field for defined variable is not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=62594 Dieter Praas changed: What|Removed |Added Blocks|107739 |129294 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107739 [Bug 107739] [META] Field bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=129294 [Bug 129294] [META] Variable field bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 69464] Fields, Show Variable displays 0 in the first paragraph when Set Variable is in the header
https://bugs.documentfoundation.org/show_bug.cgi?id=69464 Dieter Praas changed: What|Removed |Added Blocks|107739 |129294 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107739 [Bug 107739] [META] Field bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=129294 [Bug 129294] [META] Variable field bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
