[Libreoffice-bugs] [Bug 119927] [META] MariaDB C API
https://bugs.documentfoundation.org/show_bug.cgi?id=119927 Bug 119927 depends on bug 126852, which changed state. Bug 126852 Summary: MYSQL/MariaDB native connector: Column Type "TEXT" is reported as "VARCHAR" https://bugs.documentfoundation.org/show_bug.cgi?id=126852 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 126852] MYSQL/MariaDB native connector: Column Type "TEXT" is reported as "VARCHAR"
https://bugs.documentfoundation.org/show_bug.cgi?id=126852 Robert Großkopf changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Robert Großkopf --- (In reply to Julien Nabet from comment #5) > Robert: I took a look at > https://chartio.com/resources/tutorials/understanding-strorage-sizes-for- > mysql-text-data-types/, are you sure it should be "MEMO TEXT" and not "MEMO > TINYTEXT" ? The original MySQL/MariaDB datatype is TEXT. If you open the tableeditor in Base you see Memo[TEXT]. "Memo" is only a description in Base, has nothing to do with MySQL/MariaDB. TEXT is the type an it will have a maximum of 65525 characters. TINYTEXT has a maximum of 255 characters. This bug has been fixed now. The code for creating a table is misleading. Must be CREATE TABLE strtest (d TEXT); without a defined length. This will work right now with LO 6.3.4.1, fails with LO 6.2.6.2. I will set this one to RESOLVED FIXED -- 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 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Bug 10 depends on bug 118947, which changed state. Bug 118947 Summary: FILEOPEN:DOCX: table style is overriding para-style font size https://bugs.documentfoundation.org/show_bug.cgi?id=118947 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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-ux-advise] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 --- Comment #32 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/6de43b0591cf3bf4b0c584153aaf4bc21e9d2698 tdf#127294 add tip about removing multiple hyperlinks It will be available in 6.4.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-ux-advise] [Bug 127294] Add more tips of the day (and make it module-specific eventually)
https://bugs.documentfoundation.org/show_bug.cgi?id=127294 Commit Notification changed: What|Removed |Added Whiteboard|target:6.5.0|target:6.5.0 target:6.4.0.1 -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[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 #32 from Commit Notification --- Seth Chaiklin committed a patch related to this issue. It has been pushed to "libreoffice-6-4": https://git.libreoffice.org/core/commit/6de43b0591cf3bf4b0c584153aaf4bc21e9d2698 tdf#127294 add tip about removing multiple hyperlinks It will be available in 6.4.0.1. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs 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 Commit Notification changed: What|Removed |Added Whiteboard|target:6.5.0|target:6.5.0 target:6.4.0.1 -- 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-commits] core.git: cui/inc
cui/inc/tipoftheday.hrc |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
New commits:
commit b6c357506740d14611603a4611f4aacaffe4ee13
Author: Seth Chaiklin
AuthorDate: Fri Nov 29 16:18:55 2019 +0200
Commit: Heiko Tietze
CommitDate: Sat Nov 30 08:26:35 2019 +0100
revised text for existing tips
Change-Id: I8a1c03d2282ad20a58dada4507fcab8d822f481e
Reviewed-on: https://gerrit.libreoffice.org/84064
Tested-by: Jenkins
Reviewed-by: Heiko Tietze
diff --git a/cui/inc/tipoftheday.hrc b/cui/inc/tipoftheday.hrc
index f184fd64f82b..eb25bf339906 100644
--- a/cui/inc/tipoftheday.hrc
+++ b/cui/inc/tipoftheday.hrc
@@ -55,7 +55,7 @@ const std::tuple
TIPOFTHEDAY_STRINGARRAY[] =
{ NC_("RID_CUI_TIPOFTHEDAY", "Find all expressions in brackets per Edit >
Find & Replace > Find > \\([^)]+\\) (check ‘Regular expressions’)"), "",
"tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Select a different icon set from Tools >
Options > %PRODUCTNAME > View > User Interface > Icon style."), "", ""},
{ NC_("RID_CUI_TIPOFTHEDAY", "You can display a number as a fraction
(0.125 = 1/8): Format > Cells, Number > Fraction."), "", "tipoftheday_c.png"},
- { NC_("RID_CUI_TIPOFTHEDAY", "To remove a hyperlink but keep its text,
right click on the hyperlink, and use 'Remove Hyperlink'."), "",
"tipoftheday_w.png"},
+ { NC_("RID_CUI_TIPOFTHEDAY", "To remove a hyperlink but keep its text,
right-click on the hyperlink, and use 'Remove Hyperlink'."), "",
"tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To remove several hyperlinks at once,
select the text with the hyperlinks, then right-click and use ‘Remove
Hyperlink’."), "", "tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To quickly zoom in the selection, press /
(divide key) on the number pad. Press * to restore entire page in screen."),
"", "tipoftheday_d.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Click a column field (row) PivotTable and
press F12 to group data. Choices adapt to content: Date (month, quarter, year),
number (classes)"), "", "tipoftheday_c.png"},
@@ -233,7 +233,7 @@ const std::tuple
TIPOFTHEDAY_STRINGARRAY[] =
{ NC_("RID_CUI_TIPOFTHEDAY", "Click at the beginning (end) of a section
and press Alt+Enter to insert a paragraph before (after) the section."), "",
"tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "%PRODUCTNAME has a template center to
create good looking documents - check it out."),
"http://templates.libreoffice.org/template-center;, ""},
{ NC_("RID_CUI_TIPOFTHEDAY", "Calculate loan repayments with Calc: eg.
PMT(2%/12;36;2500) interest rate per payment period 2%/12, 36 months, loan
amount 2500."),
"https://help.libreoffice.org/%PRODUCTVERSION/%LANGUAGENAME/text/scalc/01/04060119.html?DbPAR=CALC#bm_id3149577;,
"tipoftheday_c.png"}, //local help missing
- { NC_("RID_CUI_TIPOFTHEDAY", "Can not find what you want with the VLOOKUP
Calc function? With INDEX and MATCH you can do everything!"),
"https://help.libreoffice.org/%PRODUCTVERSION/%LANGUAGENAME/text/scalc/01/04060109.html;,
"tipoftheday_c.png"}, //local help missing
+ { NC_("RID_CUI_TIPOFTHEDAY", "Cannot find what you want with the VLOOKUP
function in Calc? With INDEX and MATCH you can do everything!"),
"https://help.libreoffice.org/%PRODUCTVERSION/%LANGUAGENAME/text/scalc/01/04060109.html;,
"tipoftheday_c.png"}, //local help missing
{ NC_("RID_CUI_TIPOFTHEDAY", "Want to show hidden column A? Click a cell
in column B, press the left mouse button, move the mouse to the left, release.
Then switch it on via Format > Columns > Show."), "", "tipoftheday_c.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To change the number of a page in Writer,
go to the properties of the first paragraph and at the Text Flow tab check
Break > Insert and enter the number."), "", "tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Run %PRODUCTNAME in any browser via
rollApp."), "https://www.rollapp.com/app/lowriter;, ""},
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] core.git: Branch 'libreoffice-6-4' - cui/inc
cui/inc/tipoftheday.hrc |1 +
1 file changed, 1 insertion(+)
New commits:
commit 6de43b0591cf3bf4b0c584153aaf4bc21e9d2698
Author: Seth Chaiklin
AuthorDate: Thu Nov 14 15:14:12 2019 +0200
Commit: Heiko Tietze
CommitDate: Sat Nov 30 08:25:57 2019 +0100
tdf#127294 add tip about removing multiple hyperlinks
Change-Id: I465d459dce8bd279cb3052d4563340efc3092ec7
Reviewed-on: https://gerrit.libreoffice.org/82691
Tested-by: Jenkins
Reviewed-by: Heiko Tietze
(cherry picked from commit e95f32217b074e320d79bb6c35b445099b998cf0)
Reviewed-on: https://gerrit.libreoffice.org/84065
diff --git a/cui/inc/tipoftheday.hrc b/cui/inc/tipoftheday.hrc
index 29a8e504a630..76d25b83c3c1 100644
--- a/cui/inc/tipoftheday.hrc
+++ b/cui/inc/tipoftheday.hrc
@@ -56,6 +56,7 @@ const std::tuple
TIPOFTHEDAY_STRINGARRAY[] =
{ NC_("RID_CUI_TIPOFTHEDAY", "Select a different icon set from Tools >
Options > %PRODUCTNAME > View > User Interface > Icon style."), "", ""},
{ NC_("RID_CUI_TIPOFTHEDAY", "You can display a number as a fraction
(0.125 = 1/8): Format > Cells, Number > Fraction."), "", "tipoftheday_c.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To remove a hyperlink but keep its text,
right click on the hyperlink, and use 'Remove Hyperlink'."), "",
"tipoftheday_w.png"},
+ { NC_("RID_CUI_TIPOFTHEDAY", "To remove several hyperlinks at once,
select the text with the hyperlinks, then right click and use ‟Remove
Hyperlink”"), "", "tipoftheday_w.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "To quickly zoom in the selection, press /
(divide key) on the number pad. Press * to restore entire page in screen."),
"", "tipoftheday_d.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "Click a column field (row) PivotTable and
press F12 to group data. Choices adapt to content: Date (month, quarter, year),
number (classes)"), "", "tipoftheday_c.png"},
{ NC_("RID_CUI_TIPOFTHEDAY", "You can restarts the slide show after a
pause specified at Slide Show > Slide Show Settings > Loop and repeat."), "",
"tipoftheday_i.png"},
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 129104] When saving user-defined menus, standard menu entries are (partially) lost.
https://bugs.documentfoundation.org/show_bug.cgi?id=129104 Heiko Tietze changed: What|Removed |Added CC||heiko.tietze@documentfounda ||tion.org, ||xiscofa...@libreoffice.org URL||https://listarchives.libreo ||ffice.org/de/discuss/msg233 ||41.html --- Comment #4 from Heiko Tietze --- I see the entry "More breaks >" with Version: 6.2.8.2 Build ID: 6.2.8-3 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: kde5; Locale: de-DE (en_US.UTF-8); 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
feature/skia merged to master - compiling FIXED for Ubuntu 16.04
Thanks for adjusting that Luboš. I can confirm that compiling "just works" again for Ubuntu 16.04. Justin ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 129110] EDITING: Tabbed dialog box has insufficient contrast on active tab if macOS Increase Contrast selected
https://bugs.documentfoundation.org/show_bug.cgi?id=129110 --- Comment #1 from Chas Belov --- Still an issue on 6.2.8.2. -- 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 129110] New: EDITING: Tabbed dialog box has insufficient contrast on active tab if macOS Increase Contrast selected
https://bugs.documentfoundation.org/show_bug.cgi?id=129110 Bug ID: 129110 Summary: EDITING: Tabbed dialog box has insufficient contrast on active tab if macOS Increase Contrast selected Product: LibreOffice Version: 6.0.7.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: docor...@sonic.net Created attachment 156196 --> https://bugs.documentfoundation.org/attachment.cgi?id=156196=edit Screen shot of Fields dialog while Increase Contrast has been set If I have macOS Accessibility Display preferences set to Increase Contrast, then the active tab on tabbed dialog boxes is unreadable. Steps on macOS Mojave 10.14.6: 1. Apple menu > System Preferences > Accessibility > Display 2. Check Increase Contrast 3. Launch LibreOffice 4. Insert > Fields > More fields 5. Click Variables Expected result: I can read the labels on all tabs Actual result: I can read the labels on all inactive tabs, but not on the active tab 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 104450] [META] DOCX (OOXML) file opening issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104450 Bug 104450 depends on bug 39179, which changed state. Bug 39179 Summary: FILEOPEN: Writer has dump and takes very long to open DOCX with 973 footnotes https://bugs.documentfoundation.org/show_bug.cgi?id=39179 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- 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 39179] FILEOPEN: Writer has dump and takes very long to open DOCX with 973 footnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=39179 Justin L changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE --- Comment #52 from Justin L --- bug 76260 has much better commentary and is definitely talking about the same problem. Marking this one as the duplicate. *** This bug has been marked as a duplicate of bug 76260 *** -- 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 76260] FILEOPEN: slow loading and dump of .docx with lots of footnotes (see Comment 27 and Comment 43)
https://bugs.documentfoundation.org/show_bug.cgi?id=76260 Justin L changed: What|Removed |Added CC||noreply+23713@documentfound ||ation.org --- Comment #48 from Justin L --- *** Bug 39179 has been marked as a duplicate of 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 109425] Libreoffice Notebookbar is not exposing accessible events needed for screen reader users.
https://bugs.documentfoundation.org/show_bug.cgi?id=109425 --- Comment #24 from Jim Raykowski --- This patch makes Before Text Indent, After Text Indent, Above Paragraph Spacing and Below Paragraph Spacing controls used in notebookbar tabbed compact layout focus correctly when using keyboard navigation. It also corrects images used for before, after, and above controls. https://gerrit.libreoffice.org/#/c/84103/ -- 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 39179] FILEOPEN: Writer has dump and takes very long to open DOCX with 973 footnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=39179 Justin L changed: What|Removed |Added CC||jl...@mail.com --- Comment #51 from Justin L --- The entire footnote.xml file is opened and read for every single footnote reference. A huge speed-up could be attained by parsing once and storing the result in an array (at the cost of theoretically infinite memory). But I'm an inadequate programmer to handle that task... Some useful commentary from commit 330b860205c7ba69dd6603f65324d0f89ad9cd5f Author: Miklos Vajna Date: Wed Sep 4 16:08:49 2013 +0200 tdf#68787 DOCX import: handle when w:separator is missing for footnotes ... 2) The footnote stream isn't read by the importer, only when the main stream references the footnote one, the relevant part of it is parsed. At the moment we always parse the first (special, "separator") entry in the footnote stream, that may be optimized later if it becomes a bottleneck. That optimization of only parsing the separator once instead of 973 times yields only a minor improvement (<10%). gerrit.libreoffice.org/84104 -- 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 109425] Libreoffice Notebookbar is not exposing accessible events needed for screen reader users.
https://bugs.documentfoundation.org/show_bug.cgi?id=109425 --- Comment #23 from Jim Raykowski --- Here is a patch to make the send mail button keyboard accessible in the notebookbar tabbed compact tools tab: https://gerrit.libreoffice.org/#/c/84101/ -- 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 109425] Libreoffice Notebookbar is not exposing accessible events needed for screen reader users.
https://bugs.documentfoundation.org/show_bug.cgi?id=109425 --- Comment #22 from Jim Raykowski --- Here is a patch to provide keyboard access to the grow and shrink buttons in notebookbar contextual single and to show print preview controls. https://gerrit.libreoffice.org/#/c/84105/ -- 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 120994] Track Changes don't toggle the button Record in the Contextual Groups interface
https://bugs.documentfoundation.org/show_bug.cgi?id=120994 Sabri Unal changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Sabri Unal --- It seems fixed. -- 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 103170] [META] Notebookbar Contextual
https://bugs.documentfoundation.org/show_bug.cgi?id=103170 Bug 103170 depends on bug 120994, which changed state. Bug 120994 Summary: Track Changes don't toggle the button Record in the Contextual Groups interface https://bugs.documentfoundation.org/show_bug.cgi?id=120994 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- 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 129109] EDITING: Inserting a text variable field needs to be more intuitive
https://bugs.documentfoundation.org/show_bug.cgi?id=129109 --- Comment #1 from Chas Belov --- Confirmed still an issue in 6.2.8.2. -- 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 129109] New: EDITING: Inserting a text variable field needs to be more intuitive
https://bugs.documentfoundation.org/show_bug.cgi?id=129109 Bug ID: 129109 Summary: EDITING: Inserting a text variable field needs to be more intuitive Product: LibreOffice Version: 6.0.7.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: docor...@sonic.net It is not clear in the UI or LibreOffice help that in order to be able to test a variable containing a text value for a logic condition, you much choose the Text format when creating that variable so that the variable is assigned a Text type, and that leaving it as a General variable will assign the wrong (numeric) type. The usability of this needs to be improved. Demonstration of issue Steps: 1. Insert variable varA with value "is" (without the quotes) -- a. Insert > Fields > More fields > Variables > Set Variable -- b. Name: varA -- c. Value: is Alternative 1: Expected result: Default format General is replaced with Text automatically Actual result: Default format General remains selected Alternative 2: Expected result: Warning appears that the value I entered is not numeric /or/ Warning appears that the value I entered requires the Text format. Actual result: No indication that anything is amiss. -- d. Click Insert Alternative 3: Expected result: Error dialog that the value and type don't match. Actual result: Field is inserted with wrong (numeric) type. -- 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 97432] Breakpoints ignore when macro first run
https://bugs.documentfoundation.org/show_bug.cgi?id=97432 --- Comment #8 from himajin100...@gmail.com --- https://opengrok.libreoffice.org/xref/core/basic/source/runtime/runtime.cxx?r=f853ec31#4220 Somehow static_cast(nFlags) is 0 when the code fails to break, while in successful cases it's 1. -- 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 34722] FILEOPEN: Text boxes are not shown in generated .doc documents
https://bugs.documentfoundation.org/show_bug.cgi?id=34722 --- Comment #23 from Aurimas Fišeras --- Bug is still present in: Versija: 6.3.3.2 Darinio identifikatorius: 1:6.3.3-0ubuntu2 Procesoriaus gijos: 8; OS:Linux 5.3; Sąsajos pateikimas: numatytasis; VCL: gtk3; Lokalė: lt-LT (lt_LT.UTF-8); Sąsajos kalba: lt-LT And: Versija: 6.5.0.0.alpha0+ Darinio identifikatorius: 63634738dd03cc74806ce6843c16ff5e51a371a0 Procesoriaus gijos: 8; OS:Linux 5.3; Sąsajos pateikimas: Skia/Vulkan; VCL: gtk3; Lokalė: lt-LT (lt_LT.UTF-8); Sąsajos kalba: lt-LT -- 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 129049] a frame positioned relative to the page text area is converted to relative to the entire page.
https://bugs.documentfoundation.org/show_bug.cgi?id=129049 Dieter Praas changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Dieter Praas --- Kenn wrote in private: hi Dieter, I cannot reproduce the problem @ this time, even after a restart so close the bug. thanks for your efforts. if the problem reappears & i'm sure it will, i'll start over. => RESOLVED WORKSFORME -- 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-commits] core.git: include/toolkit toolkit/source
include/toolkit/awt/vclxtopwindow.hxx | 58 ++
toolkit/source/awt/vclxtopwindow.cxx | 87 ++
2 files changed, 44 insertions(+), 101 deletions(-)
New commits:
commit 2d594080628d66649e5f01455adb50e3d49cb195
Author: Noel Grandin
AuthorDate: Fri Nov 29 10:03:10 2019 +0200
Commit: Noel Grandin
CommitDate: Sat Nov 30 07:05:02 2019 +0100
merge classes VCLXTopWindow_Base and VCLXTopWindow
Change-Id: I4c0718d2947449fa076b0afd3046587c73784558
Reviewed-on: https://gerrit.libreoffice.org/84035
Tested-by: Jenkins
Reviewed-by: Noel Grandin
diff --git a/include/toolkit/awt/vclxtopwindow.hxx
b/include/toolkit/awt/vclxtopwindow.hxx
index 188f128f793e..9db6e7d51d24 100644
--- a/include/toolkit/awt/vclxtopwindow.hxx
+++ b/include/toolkit/awt/vclxtopwindow.hxx
@@ -24,33 +24,32 @@
#include
#include
-#include
+#include
#include
namespace com { namespace sun { namespace star { namespace awt { class
XMenuBar; } } } }
-typedef ::cppu::ImplHelper1 < css::awt::XTopWindow2
+typedef ::cppu::ImplHelper2 < css::awt::XTopWindow2,
css::awt::XSystemDependentWindowPeer
> VCLXTopWindow_XBase;
-typedef ::cppu::ImplHelper1 < css::awt::XSystemDependentWindowPeer
-> VCLXTopWindow_SBase;
-class VCLXTopWindow_Base :public VCLXTopWindow_XBase
-,public VCLXTopWindow_SBase
-{
-protected:
-virtual vcl::Window* GetWindowImpl() = 0;
-virtual ::comphelper::OInterfaceContainerHelper2&
GetTopWindowListenersImpl() = 0;
-
-VCLXTopWindow_Base();
+// class VCLXTopWindow
+class VCLXTopWindow: public VCLXTopWindow_XBase,
+ public VCLXContainer
+{
public:
-virtual ~VCLXTopWindow_Base();
+VCLXTopWindow();
+virtual ~VCLXTopWindow() override;
+
+// css::uno::XInterface
+css::uno::Any SAL_CALL queryInterface( const css::uno::Type & rType )
override;
+void SAL_CALL acquire() throw() override { OWeakObject::acquire(); }
+void SAL_CALL release() throw() override { OWeakObject::release(); }
-// XInterface equivalents
-css::uno::Any SAL_CALL queryInterface( const css::uno::Type & rType )
override;
-// XTypeProvider equivalents
-css::uno::Sequence< css::uno::Type > SAL_CALL getTypes() override;
+// css::lang::XTypeProvider
+css::uno::Sequence< css::uno::Type > SAL_CALL getTypes() override;
+css::uno::Sequence< sal_Int8 > SAL_CALL
getImplementationId() override;
// css::awt::XSystemDependentWindowPeer
css::uno::Any SAL_CALL getWindowHandle( const css::uno::Sequence< sal_Int8
>& ProcessId, sal_Int16 SystemType ) override;
@@ -69,31 +68,6 @@ public:
virtual void SAL_CALL setIsMinimized( sal_Bool _isminimized ) override;
virtual ::sal_Int32 SAL_CALL getDisplay() override;
virtual void SAL_CALL setDisplay( ::sal_Int32 _display ) override;
-};
-
-
-// class VCLXTopWindow
-
-
-class VCLXTopWindow: public VCLXTopWindow_Base,
- public VCLXContainer
-{
-protected:
-virtual vcl::Window* GetWindowImpl() override;
-virtual ::comphelper::OInterfaceContainerHelper2&
GetTopWindowListenersImpl() override;
-
-public:
-VCLXTopWindow();
-virtual ~VCLXTopWindow() override;
-
-// css::uno::XInterface
-css::uno::Any SAL_CALL queryInterface( const css::uno::Type & rType )
override;
-voidSAL_CALL acquire() throw() override {
OWeakObject::acquire(); }
-voidSAL_CALL release() throw() override {
OWeakObject::release(); }
-
-// css::lang::XTypeProvider
-css::uno::Sequence< css::uno::Type > SAL_CALL getTypes() override;
-css::uno::Sequence< sal_Int8 > SAL_CALL
getImplementationId() override;
static void ImplGetPropertyIds( std::vector< sal_uInt16 > );
virtual voidGetPropertyIds( std::vector< sal_uInt16 > ) override
{ return ImplGetPropertyIds( aIds ); }
diff --git a/toolkit/source/awt/vclxtopwindow.cxx
b/toolkit/source/awt/vclxtopwindow.cxx
index f612851a8236..544cc60622ae 100644
--- a/toolkit/source/awt/vclxtopwindow.cxx
+++ b/toolkit/source/awt/vclxtopwindow.cxx
@@ -46,38 +46,14 @@ using ::com::sun::star::uno::Type;
using ::com::sun::star::uno::Any;
using ::com::sun::star::lang::IndexOutOfBoundsException;
-VCLXTopWindow_Base::VCLXTopWindow_Base()
-{
-}
-
-VCLXTopWindow_Base::~VCLXTopWindow_Base()
-{
-}
-
-Any VCLXTopWindow_Base::queryInterface( const Type & rType )
-{
-css::uno::Any aRet( VCLXTopWindow_XBase::queryInterface( rType ) );
-
-if (!aRet.hasValue())
-aRet = VCLXTopWindow_SBase::queryInterface( rType );
-
-return aRet;
-}
-Sequence< Type > VCLXTopWindow_Base::getTypes()
-{
-Sequence< Type > aTypes( VCLXTopWindow_XBase::getTypes() );
-aTypes = ::comphelper::concatSequences( aTypes,
VCLXTopWindow_SBase::getTypes() );
-
[Libreoffice-bugs] [Bug 126456] Writer Export To PDF button's hint under MacOS, Chinese characters are not displayed properly
https://bugs.documentfoundation.org/show_bug.cgi?id=126456 Dieter Praas changed: What|Removed |Added Blocks||113194 CC||dgp-m...@gmx.de Component|Writer |Printing and PDF export Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113194 [Bug 113194] [META] Simplified Chinese (zh_CN) language-specific CJK issues -- 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 113194] [META] Simplified Chinese (zh_CN) language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113194 Dieter Praas changed: What|Removed |Added Depends on||126456 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126456 [Bug 126456] Writer Export To PDF button's hint under MacOS, Chinese characters are not displayed properly -- 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 113194] [META] Simplified Chinese (zh_CN) language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113194 Dieter Praas changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=83 | |066 | -- 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 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Dieter Praas changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |3194| -- 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 113193] [META] Traditional Chinese (zh_TW, zh_HK) language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113193 Dieter Praas changed: What|Removed |Added Blocks||83066 See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=83 | |066 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83066 [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues -- 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 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Dieter Praas changed: What|Removed |Added Depends on||113193 See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |3193| Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113193 [Bug 113193] [META] Traditional Chinese (zh_TW, zh_HK) language-specific CJK issues -- 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 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Dieter Praas changed: What|Removed |Added Depends on||113195 See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |3195| Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113195 [Bug 113195] [META] Japanese language-specific CJK issues -- 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 113195] [META] Japanese language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113195 Dieter Praas changed: What|Removed |Added Blocks||83066 See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=83 | |066 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83066 [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues -- 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 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Dieter Praas changed: What|Removed |Added Depends on||113194 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113194 [Bug 113194] [META] Simplified Chinese (zh_CN) language-specific CJK issues -- 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 113194] [META] Simplified Chinese (zh_CN) language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113194 Dieter Praas changed: What|Removed |Added Blocks||83066 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83066 [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues -- 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 113196] [META] Korean language-specific CJK issues
https://bugs.documentfoundation.org/show_bug.cgi?id=113196 Dieter Praas changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=83 | |066 | Blocks||83066 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83066 [Bug 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues -- 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 83066] [META] CJK (Chinese, Japanese, Korean, and Vietnamese) language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83066 Dieter Praas changed: What|Removed |Added Depends on||113196 See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=11 | |3196| Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113196 [Bug 113196] [META] Korean language-specific CJK issues -- 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 129108] New: Text in the 'Tip of the Day' window does not word wrap and so disappears off the edge
https://bugs.documentfoundation.org/show_bug.cgi?id=129108 Bug ID: 129108 Summary: Text in the 'Tip of the Day' window does not word wrap and so disappears off the edge Product: LibreOffice Version: 6.3.3.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: libreoff...@boz.33mail.com Description: Each time I open Libreoffice the 'Tip of the Day'window appears. I can see the first few words of the tip but most of it is not shown because the text does not word wrap, instead it is all on one line and vanishes as it goes past the edge of the window. It used to word wrap and was therefore easy to read, but now I can only see the words if I select the text and move the cursor along its length to bring it within the window a few words at a time. Steps to Reproduce: 1.Start Libreoffice 2 that's it 3. Actual Results: Tip of the Day opens, only first three or four words visible Expected Results: I expect the actual results stated above because thgrough experience I know it will not do what it should by wrapping the text to fit inside the window Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Renderer: Intel(R) HD Graphics 630 Vendor: Intel Version: 4.6.0 - Build 26.20.100.7463 Shading language version: 4.60 - Build 26.20.100.7463 Max texture size: 16384 x 16384 Max vertex texture image units: 32 Max texture image units: 32 Max geometry texture units: 32 Max anisotropic filtering value: 16 Max viewport size: 16384 x 16384 Max Clip Distances: 8 Max samples: 16 GL Extensions: 249 GL_ARB_tessellation_shader GL_ARB_half_float_pixel GL_EXT_compiled_vertex_array GL_KHR_texture_compression_astc_hdr GL_KHR_texture_compression_astc_ldr GL_WIN_swap_hint GL_EXT_packed_depth_stencil GL_EXT_texture_lod_bias GL_EXT_direct_state_access GL_INTEL_map_texture GL_ARB_color_buffer_float GL_ARB_shader_image_load_store GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_draw_instanced GL_ARB_derivative_control GL_EXT_draw_buffers2 GL_ARB_viewport_array GL_ARB_gpu_shader_fp64 GL_ARB_pipeline_statistics_query GL_EXT_texture_shared_exponent GL_ARB_draw_elements_base_vertex GL_ARB_arrays_of_arrays GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_window_pos GL_ARB_explicit_attrib_location GL_ARB_texture_float GL_INTEL_conservative_rasterization GL_ARB_point_parameters GL_ARB_texture_compression GL_KHR_no_error GL_EXT_transform_feedback GL_ARB_depth_buffer_float GL_EXT_timer_query WGL_EXT_create_context_es_profile GL_ARB_vertex_buffer_object GL_EXT_packed_float GL_ARB_pixel_buffer_object WGL_ARB_create_context_robustness GL_INTEL_multi_rate_fragment_shader GL_ARB_separate_shader_objects GL_ARB_buffer_storage GL_ARB_query_buffer_object GL_ARB_fragment_program_shadow WGL_EXT_swap_control GL_ARB_shading_language_100 GL_ARB_program_interface_query WGL_ARB_extensions_string GL_KHR_debug GL_ARB_compute_shader GL_ARB_get_texture_sub_image GL_ARB_texture_storage GL_EXT_packed_pixels GL_EXT_blend_func_separate GL_ARB_gpu_shader5 GL_INTEL_fragment_shader_ordering GL_EXT_texture3D GL_ARB_texture_env_crossbar GL_EXT_stencil_wrap GL_EXT_shader_framebuffer_fetch GL_ARB_ES3_compatibility GL_ARB_fragment_shader_interlock GL_ARB_texture_swizzle GL_ARB_transpose_matrix GL_ARB_cl_event GL_EXT_texture_compression_s3tc GL_ARB_vertex_program GL_EXT_texture_sRGB WGL_EXT_pixel_format_packed_float GL_ARB_texture_rectangle GL_ARB_depth_clamp GL_ARB_shading_language_packing GL_ARB_texture_cube_map_array GL_ARB_framebuffer_sRGB GL_ARB_texture_env_add GL_ARB_texture_rg GL_ARB_framebuffer_no_attachments GL_ARB_blend_func_extended WGL_EXT_extensions_string GL_ARB_vertex_attrib_64bit GL_EXT_texture_sRGB_decode GL_ARB_multi_draw_indirect GL_ARB_texture_gather GL_ARB_half_float_vertex GL_SGIS_texture_edge_clamp WGL_EXT_create_context_es2_profile GL_ARB_debug_output GL_ARB_texture_cube_map GL_EXT_shadow_funcs GL_SGIS_texture_lod GL_EXT_texture_filter_anisotropic GL_ARB_shader_draw_parameters GL_ARB_spirv_extensions GL_EXT_multi_draw_arrays GL_ARB_invalidate_subdata GL_EXT_texture_rectangle GL_ARB_robustness_isolation GL_ARB_vertex_array_object GL_ARB_explicit_uniform_location GL_ARB_shadow GL_ARB_vertex_array_bgra GL_ARB_shader_group_vote GL_SGIS_generate_mipmap GL_EXT_blend_minmax GL_ARB_texture_filter_anisotropic WGL_ARB_pixel_format GL_ARB_texture_query_levels GL_ARB_point_sprite GL_ARB_depth_texture GL_ARB_fragment_layer_viewport GL_ARB_copy_buffer WGL_ARB_make_current_read WGL_ARB_pixel_format_float GL_ARB_indirect_parameters GL_ARB_bindless_texture GL_3DFX_texture_compression_FXT1 GL_ARB_robustness GL_ARB_get_program_binary GL_ARB_conditional_render_inverted GL_INTEL_performance_query GL_ARB_transform_feedback2
[Libreoffice-bugs] [Bug 34355] Option to show track changes in margin is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=34355 --- Comment #87 from RTEUA --- This means that if those resources and employment opportunities are the weapons to win trade war then China will take competitive advantage against the USA. https://essaybaron.com/hire-a-freelance-writter -- 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-ux-advise] [Bug 34355] Option to show track changes in margin is missing
https://bugs.documentfoundation.org/show_bug.cgi?id=34355 --- Comment #87 from RTEUA --- This means that if those resources and employment opportunities are the weapons to win trade war then China will take competitive advantage against the USA. https://essaybaron.com/hire-a-freelance-writter -- You are receiving this mail because: You are on the CC list for the bug. ___ Libreoffice-ux-advise mailing list Libreoffice-ux-advise@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise
[Libreoffice-bugs] [Bug 129089] Using LibreOffice Writer version 6.3.3 I can modify all of the styles except those pertaining to the footnotes with an imported document.
https://bugs.documentfoundation.org/show_bug.cgi?id=129089 Dieter Praas changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||dgp-m...@gmx.de Ever confirmed|0 |1 --- Comment #2 from Dieter Praas --- (In reply to Pen from comment #0) > Description: > I had this problem before and I thought it had been worked on, since I > previously reported it. So there is already a bug report aout your problem? > I am using Windows 10. The file is an RTF file, > which I opened in LibreOffice Writer. Attached file is odt-file. And I can't reproduce your problem there. So please, if you've reported the problem before, give informations about it (because it's a duplicate then). If it's a new report, please attach rft-file. => 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 129103] Writer: keyboard shortcuts turned off for read-only documents
https://bugs.documentfoundation.org/show_bug.cgi?id=129103 Dieter Praas changed: What|Removed |Added CC||dgp-m...@gmx.de Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Dieter Praas --- I can't confirm this with Version: 6.4.0.0.beta1 (x64) Build ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920 CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: GL; VCL: win; Locale: de-DE (de_DE); UI-Language: en-GB Calc: threaded To be certain the reported issue is not related to corruption in the user profile, could you please reset your Libreoffice profile (https://wiki.documentfoundation.org/UserProfile) and re-test? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the issue is still present -- 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 84144] Sections hiding opposite to condition
https://bugs.documentfoundation.org/show_bug.cgi?id=84144 Mike Kaganski changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG --- Comment #6 from Mike Kaganski --- This works as intended, and is not a bug; but please see at the end of the comment. Inserting a "Set variable" field *for the first time*, you *define* a variable in the document; and also *define its type*, which can be *numeric* or *textual*. After the definition, you can't change the type (until you remove the variable from document using "cross" button in "Set variable" insertion dialog). By default, all variables are created of numeric type. Setting a variable's type is done by assigning it "Text" *format* when creating it. When a variable is created numeric, i.e. not assigned "Text" format when created, its value is treated as a formula, and its result is converted to number. E.g., putting "is" with quotes would make the variable equal to result of conversion of text "is" to a number, which is 0. Putting "123a456" in quotes would result in number 123, because conversion to number stops at non-numeric character "a". `1+2` (without quotes) gives 3. Putting `pi` (without quotes) into the value of the numeric variable produces result of 3.14..., using one of predefined values [1] (note that value names are case-insensitive). When you have created a numeric variable varA with value 3, creating numeric varB with formula `varA + 1` will give 4. For a numeric variable, there is a specific situation when you put an undefined name into its value box. E.g., creating numeric varA with value `is` without quotes, when no variable `is` was defined, produces varA variable with *empty* value, which e.g. also produces empty results of formulas like `varA + 1`. When a variable is defined textual (by setting its format to Text upon its creation), anything you write into the value box is treated as plain string (except when you put an existing variable name); e.g., putting `is` without quotes into the value box (assuming there's no variable `is` predefined) will produce string "is", which might be tested using condition `var EQ "is"` [2]; putting "is" *with* quotes into the value box will produce 4-character string *containing the quotes*, so the condition `var EQ "is"` would fail this time; `1+2` would produce string "1+2". But when you have a variable txtA containing "AAA", and you create another textual txtB with value `txtA`, txtB will contain AAA. Note again that trying to change existing variable type after creation will not work, neither in "Set variable field", nor in "Show variable", "Input field", or others. So your steps in comment 0 lack a step between 1.b and 1.c, which would be 1.b.1. Format: Text With that, your document will work => NOTABUG. Now I agree that there a problem with the Set Variable fields, worth a separate issue: The aspects of *creation* of a variable; *variables having a type*; and other variable manipulations (e.g., that variables don't get deleted when the last field setting/using it is removed; or inability to change type; or empty result when using undefined names in numeric variables; or using predefined variable names in textual variables) are unclear, not intuitive, and not well documented and represented in UI. There's tdf#111888 regarding one of aspects of variable manipulation, but unrelated to this issue (which is about variable types). Please create a separate issue(s) regarding documentation and usability about these problems. [1] https://help.libreoffice.org/6.3/en-US/text/swriter/02/1402.html [2] https://help.libreoffice.org/6.3/en-US/text/swriter/01/04090200.html -- 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 107738] [META] Section bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107738 Bug 107738 depends on bug 84144, which changed state. Bug 84144 Summary: Sections hiding opposite to condition https://bugs.documentfoundation.org/show_bug.cgi?id=84144 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- 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 73035] Other: Invalid countif result on Named range
https://bugs.documentfoundation.org/show_bug.cgi?id=73035 --- Comment #2 from markwell --- Thanks for sharing the post and nice to see this here. Get the details about pets here. https://dogsfud.com/can-dogs-have-tylenol/ -- 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 54218] DIN A3 printing in Page Preview correct, Printout wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=54218 --- Comment #8 from ritariya --- https://www.google.com/;>https://www.google.com/ -- 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 54218] DIN A3 printing in Page Preview correct, Printout wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=54218 --- Comment #7 from ritariya --- https://www.google.com/;>good article -- 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 128996] Y-axis labels disappear in horizontal bar chart
https://bugs.documentfoundation.org/show_bug.cgi?id=128996 --- Comment #4 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 128996] Y-axis labels disappear in horizontal bar chart
https://bugs.documentfoundation.org/show_bug.cgi?id=128996 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 128819] Copy and paste in LOOL (Collabora Code, 4.0.8) improper initialization
https://bugs.documentfoundation.org/show_bug.cgi?id=128819 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 128442] Newly opened document/presentation does not get focus
https://bugs.documentfoundation.org/show_bug.cgi?id=128442 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 125069] 6.2.3.2 installation errors to halt
https://bugs.documentfoundation.org/show_bug.cgi?id=125069 --- Comment #4 from QA Administrators --- Dear David Jarvis, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 129047] [Feature Request] Make the LibreOffice Writer Tabbed UI Ribbon Layout Equal To Microsoft's Office Tab Ribbons Layout
https://bugs.documentfoundation.org/show_bug.cgi?id=129047 --- 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 129047] [Feature Request] Make the LibreOffice Writer Tabbed UI Ribbon Layout Equal To Microsoft's Office Tab Ribbons Layout
https://bugs.documentfoundation.org/show_bug.cgi?id=129047 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 128963] WRITER, IMPRESS: When printing, font size ist reduced to 255pt max
https://bugs.documentfoundation.org/show_bug.cgi?id=128963 --- Comment #4 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 115903] Adding paragraphs in a (multi-page) table with embedded tables is slow and cpu hogging
https://bugs.documentfoundation.org/show_bug.cgi?id=115903 --- Comment #4 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 125074] setting a template as default only works if you open it
https://bugs.documentfoundation.org/show_bug.cgi?id=125074 --- Comment #3 from QA Administrators --- Dear peter josvai, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 108915] Can't add remote file service
https://bugs.documentfoundation.org/show_bug.cgi?id=108915 --- Comment #7 from QA Administrators --- Dear Eric, 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 125069] 6.2.3.2 installation errors to halt
https://bugs.documentfoundation.org/show_bug.cgi?id=125069 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68472] UNDO incomplete: alignment not restored in cells after UNDO cells merge
https://bugs.documentfoundation.org/show_bug.cgi?id=68472 --- Comment #9 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 125074] setting a template as default only works if you open it
https://bugs.documentfoundation.org/show_bug.cgi?id=125074 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 128963] WRITER, IMPRESS: When printing, font size ist reduced to 255pt max
https://bugs.documentfoundation.org/show_bug.cgi?id=128963 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 111423] Page format not changing to "User" upon small change in page width
https://bugs.documentfoundation.org/show_bug.cgi?id=111423 --- Comment #12 from QA Administrators --- Dear Andy 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 115637] Conditional Formatting: OK, Cancel button not working (and UI objects misplaced) with Non-English UI
https://bugs.documentfoundation.org/show_bug.cgi?id=115637 --- Comment #12 from QA Administrators --- Dear Kevin Suo, 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 91894] Impress Cut & paste of a line selects the whole table
https://bugs.documentfoundation.org/show_bug.cgi?id=91894 --- Comment #6 from QA Administrators --- Dear Philippe Jung, 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 79878] Writer freezes for minutes when opening .docx due to slow XML parse
https://bugs.documentfoundation.org/show_bug.cgi?id=79878 --- Comment #27 from QA Administrators --- Dear maintel2, 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 83575] CALC: comment does not automatically remove itself when the content becomes empty
https://bugs.documentfoundation.org/show_bug.cgi?id=83575 --- Comment #11 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 103920] It closes when you delete columns from a file with 28101 lines.
https://bugs.documentfoundation.org/show_bug.cgi?id=103920 --- Comment #6 from QA Administrators --- Dear Yasin Eyigun, 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 105638] Fileopen: 165 pages DOC with simple table non responsive (column with merged cells)
https://bugs.documentfoundation.org/show_bug.cgi?id=105638 --- Comment #15 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 117925] Freeze after scrolling through document with wrapped images
https://bugs.documentfoundation.org/show_bug.cgi?id=117925 --- Comment #6 from QA Administrators --- Dear Yousuf Philips (jay) (retired), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 119638] Text boxes copied from Draw to Writer get wrapped
https://bugs.documentfoundation.org/show_bug.cgi?id=119638 --- Comment #11 from QA Administrators --- Dear Michael Zapf, 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 39015] EDITING: Can not select text starting with the beginning of a line
https://bugs.documentfoundation.org/show_bug.cgi?id=39015 --- Comment #13 from QA Administrators --- Dear Dan Essin, 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 116655] Paragraph style is automatically set to "Default" after exiting table with Alt+Enter
https://bugs.documentfoundation.org/show_bug.cgi?id=116655 --- Comment #5 from QA Administrators --- Dear McAaron, 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 56408] Writer always breaks lines at text direction change
https://bugs.documentfoundation.org/show_bug.cgi?id=56408 --- Comment #21 from QA Administrators --- Dear Lior Kaplan, 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 72412] Tables in Impress: when the background is changed, the font size changes
https://bugs.documentfoundation.org/show_bug.cgi?id=72412 --- Comment #11 from QA Administrators --- Dear Jion, 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 117529] Can't paste chart from clipboard into Writer after closing LibO in between (works for Calc/Draw) (not Gtk3)
https://bugs.documentfoundation.org/show_bug.cgi?id=117529 --- Comment #5 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 121323] Crash dragging button after un-grouping compound group
https://bugs.documentfoundation.org/show_bug.cgi?id=121323 --- Comment #8 from QA Administrators --- Dear Jim Avera, 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 60558] Microsoft Word 10 file with shapes in floating tables will not open correctly, same if resaved in MSO
https://bugs.documentfoundation.org/show_bug.cgi?id=60558 --- Comment #12 from QA Administrators --- Dear Michelle, 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 119377] Table text replaced by '0' on applying AutoFormat Style and re-opening document
https://bugs.documentfoundation.org/show_bug.cgi?id=119377 --- Comment #12 from QA Administrators --- Dear sirgillem, 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 82380] Wrong "Reached the end of the document" text with 'Find Next' and 'Find Previous'
https://bugs.documentfoundation.org/show_bug.cgi?id=82380 --- Comment #9 from QA Administrators --- Dear Prathapmuruganandam, 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 93259] Cannot correctly read cell alignments on simple spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=93259 --- Comment #6 from QA Administrators --- Dear Eric West, 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 120994] Track Changes don't toggle the button Record in the Contextual Groups interface
https://bugs.documentfoundation.org/show_bug.cgi?id=120994 --- Comment #3 from QA Administrators --- Dear Sabri Unal, 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 34722] FILEOPEN: Text boxes are not shown in generated .doc documents
https://bugs.documentfoundation.org/show_bug.cgi?id=34722 --- Comment #22 from QA Administrators --- Dear Aurimas Fišeras, 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 121558] Documents starts to scroll (unintended) when hoovering around the ruler area with highlighting bucket tool active
https://bugs.documentfoundation.org/show_bug.cgi?id=121558 --- Comment #7 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from 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 37828] rotated text is not saved correctly in doc format
https://bugs.documentfoundation.org/show_bug.cgi?id=37828 --- Comment #18 from QA Administrators --- Dear Alexandre Demers, 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 112840] Can't replace all the underlined text with nothing
https://bugs.documentfoundation.org/show_bug.cgi?id=112840 --- Comment #6 from QA Administrators --- Dear ask4support, 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 98823] FILEOPEN: .docx show incorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=98823 --- Comment #5 from QA Administrators --- Dear Alexander, 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 120715] Cursor doesn't move forward on typing space at the end of .docx file when text is centered
https://bugs.documentfoundation.org/show_bug.cgi?id=120715 --- Comment #12 from QA Administrators --- Dear justus.croskery, 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 44934] Select row; maximize spreadsheet; only part of the row is highlighted
https://bugs.documentfoundation.org/show_bug.cgi?id=44934 --- Comment #11 from QA Administrators --- Dear B.J. Herbison, 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 53504] Heading styles (Heading 1, Heading 2, etc ) lose bold formatting.
https://bugs.documentfoundation.org/show_bug.cgi?id=53504 --- Comment #8 from QA Administrators --- Dear TJT, 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 96002] Rotated text rotates by 90 degree after save/open
https://bugs.documentfoundation.org/show_bug.cgi?id=96002 --- Comment #4 from QA Administrators --- Dear mail8, 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-commits] core.git: Branch 'libreoffice-6-4' - sfx2/source uui/source
sfx2/source/dialog/filedlghelper.cxx | 10 ++-
uui/source/iahndl-authentication.cxx | 90 ++-
2 files changed, 53 insertions(+), 47 deletions(-)
New commits:
commit 8bf39e6cfd988089bd0eab0958c96f8fc3413b9d
Author: Eike Rathke
AuthorDate: Sat Nov 30 01:26:32 2019 +0100
Commit: Eike Rathke
CommitDate: Sat Nov 30 04:04:04 2019 +0100
Resolves: tdf#97086 Allow "unlimited" password length for OOXML encryption
Change-Id: I51175424e19ad02b81120c3fdea22732cd481a8d
Reviewed-on: https://gerrit.libreoffice.org/84097
Reviewed-by: Eike Rathke
Tested-by: Jenkins
(cherry picked from commit adb7106a7c805d332c8098891996a75e6ec4caf8)
Reviewed-on: https://gerrit.libreoffice.org/84100
diff --git a/sfx2/source/dialog/filedlghelper.cxx
b/sfx2/source/dialog/filedlghelper.cxx
index a6a9dc675054..8e99b47bd4bd 100644
--- a/sfx2/source/dialog/filedlghelper.cxx
+++ b/sfx2/source/dialog/filedlghelper.cxx
@@ -2660,8 +2660,11 @@ ErrCode RequestPassword(const std::shared_ptr& pCurrentFilter,
uno::Reference xInteractionHandler =
task::InteractionHandler::createWithParent(::comphelper::getProcessComponentContext(),
rParent);
// TODO: need a save way to distinguish MS filters from other filters
// for now MS-filters are the only alien filters that support encryption
-bool bMSType = !pCurrentFilter->IsOwnFormat();
-::comphelper::DocPasswordRequestType eType = bMSType ?
+const bool bMSType = !pCurrentFilter->IsOwnFormat();
+// For OOXML we can use the standard password ("unlimited" characters)
+// request, otherwise the MS limited password request is needed.
+const bool bOOXML = bMSType && lclSupportsOOXMLEncryption(
pCurrentFilter->GetFilterName());
+const ::comphelper::DocPasswordRequestType eType = bMSType && !bOOXML ?
::comphelper::DocPasswordRequestType::MS :
::comphelper::DocPasswordRequestType::Standard;
@@ -2696,8 +2699,7 @@ ErrCode RequestPassword(const std::shared_ptr& pCurrentFilter,
// TODO/LATER: The filters should show the password dialog
themself in future
if ( bMSType )
{
-// Check if filter supports OOXML encryption
-if ( lclSupportsOOXMLEncryption(
pCurrentFilter->GetFilterName() ) )
+if (bOOXML)
{
::comphelper::SequenceAsHashMap aHashData;
aHashData[ OUString( "OOXPassword" ) ] <<=
pPasswordRequest->getPassword();
diff --git a/uui/source/iahndl-authentication.cxx
b/uui/source/iahndl-authentication.cxx
index b6c74f4926db..4835a485dd2a 100644
--- a/uui/source/iahndl-authentication.cxx
+++ b/uui/source/iahndl-authentication.cxx
@@ -488,7 +488,7 @@ executePasswordDialog(
LoginErrorInfo & rInfo,
task::PasswordRequestMode nMode,
const OUString& aDocName,
-bool bMSCryptoMode,
+sal_uInt16 nMaxPasswordLen,
bool bIsPasswordToModify,
bool bIsSimplePasswordRequest )
{
@@ -508,11 +508,9 @@ executePasswordDialog(
}
else
{
-const sal_uInt16 nMaxPasswdLen = bMSCryptoMode ? 15 : 0; // 0 ->
allow any length
-
VclAbstractDialogFactory * pFact =
VclAbstractDialogFactory::Create();
ScopedVclPtr const pDialog(
-pFact->CreatePasswordToOpenModifyDialog(pParent,
nMaxPasswdLen, bIsPasswordToModify));
+pFact->CreatePasswordToOpenModifyDialog(pParent,
nMaxPasswordLen, bIsPasswordToModify));
rInfo.SetResult( pDialog->Execute() == RET_OK ?
DialogMask::ButtonsOk : DialogMask::ButtonsCancel );
rInfo.SetPassword( pDialog->GetPasswordToOpen() );
@@ -539,7 +537,7 @@ handlePasswordRequest_(
uno::Sequence< uno::Reference< task::XInteractionContinuation > > const &
rContinuations,
const OUString& aDocumentName,
-bool bMSCryptoMode,
+sal_uInt16 nMaxPasswordLen,
bool bIsPasswordToModify,
bool bIsSimplePasswordRequest = false )
{
@@ -555,7 +553,7 @@ handlePasswordRequest_(
LoginErrorInfo aInfo;
executePasswordDialog( pParent, aInfo, nMode,
-aDocumentName, bMSCryptoMode, bIsPasswordToModify,
bIsSimplePasswordRequest );
+aDocumentName, nMaxPasswordLen, bIsPasswordToModify,
bIsSimplePasswordRequest );
switch (aInfo.GetResult())
{
@@ -649,61 +647,67 @@ UUIInteractionHelper::handlePasswordRequest(
task::PasswordRequestMode nMode = task::PasswordRequestMode_PASSWORD_ENTER;
uno::Sequence< uno::Reference< task::XInteractionContinuation > > const &
rContinuations = rRequest->getContinuations();
OUString aDocumentName;
-bool bMSCryptoMode = false;
+sal_uInt16 nMaxPasswordLen = 0;// any length
bool bIsPasswordToModify= false;
bool bDoHandleRequest = false;
uno::Any aAnyRequest(rRequest->getRequest());
-task::DocumentPasswordRequest2 aDocumentPasswordRequest2;
[Libreoffice-bugs] [Bug 122652] [META] Memory problems in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=122652 Aron Budea changed: What|Removed |Added Depends on||125662 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=125662 [Bug 125662] Bad allocation crash while saving Calc with copied columns (x86) -- 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 125662] Bad allocation crash while saving Calc with copied columns (x86)
https://bugs.documentfoundation.org/show_bug.cgi?id=125662 Aron Budea changed: What|Removed |Added Blocks||122652 Version|6.4.0.0.alpha1+ |6.3.0.0.beta1+ --- Comment #6 from Aron Budea --- MarvinWWW: your bug sounds different, please open a new bug report, and attach the samples you have. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122652 [Bug 122652] [META] Memory problems in LibreOffice -- 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 129101] Image handling and memory usage horrible
https://bugs.documentfoundation.org/show_bug.cgi?id=129101 V Stuart Foote changed: What|Removed |Added Blocks||47148 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=47148 [Bug 47148] [META] Image handling problems -- 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 47148] [META] Image handling problems
https://bugs.documentfoundation.org/show_bug.cgi?id=47148 V Stuart Foote changed: What|Removed |Added Depends on||129101 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129101 [Bug 129101] Image handling and memory usage horrible -- 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 108458] Label changes for Toolbar use degrade function listing in the Customize dialog--have duplicate entries on the list
https://bugs.documentfoundation.org/show_bug.cgi?id=108458 V Stuart Foote changed: What|Removed |Added CC||tor...@yahoo.com --- Comment #31 from V Stuart Foote --- *** Bug 129102 has been marked as a duplicate of 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
