[Libreoffice-bugs] [Bug 80599] PRINTING: Print comments at end of sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=80599 --- Comment #8 from Thanos --- Must be visit here his amazing post here you can looking the full function for connect windows 10 sync settings greyed out so you need to visit here http://windowstuts.net/synchronize-settings/ and save the all setting for download thanks. -- 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-1' - sc/uiconfig
sc/uiconfig/scalc/ui/notebookbar.ui | 123 1 file changed, 123 insertions(+) New commits: commit ef6b706305737818fc2fc94267a746e28928fbaa Author: andreas kainz Date: Thu Jun 21 00:40:42 2018 +0200 NB calc: add initial chart items to object tab Change-Id: I398c4dd384d021c3e70165968b9fadaf34039959 Reviewed-on: https://gerrit.libreoffice.org/56212 Tested-by: Jenkins Reviewed-by: andreas_kainz (cherry picked from commit a777e447a7d78cd91aca09b373f36c057e8bd8e0) Reviewed-on: https://gerrit.libreoffice.org/56428 diff --git a/sc/uiconfig/scalc/ui/notebookbar.ui b/sc/uiconfig/scalc/ui/notebookbar.ui index f9a4ae7e6692..b6c40b6e3ea8 100644 --- a/sc/uiconfig/scalc/ui/notebookbar.ui +++ b/sc/uiconfig/scalc/ui/notebookbar.ui @@ -11965,6 +11965,129 @@ + +True +False +center +True + + +True +False +center +True +both +False +3 + + +True +False +.uno:ChartElementSelector + + +True +True + + + + +False +True +1 + + + + +True +False +center +vertical + + +True +False +center +True +both-horiz +False + + +True +False +.uno:FormatSelection + + +True +True + + + + +False +True +0 + + + + +True +False +center +True +both-horiz +False + + +True +False +.uno:DiagramType + + +True +True + + + + +False +True +1 + + + + +False +True +2 + + + + +True +False +5 +5 +vertical + + +False +True +5 +3 + + + ++ + + +False +True +
master build fail
Hi, My master build (up to commit https://gerrit.libreoffice.org/gitweb?p=core.git;a=commit;h=e90b7ebe137c638523923d7d2fe8bb8d8a8d75cc) failed this night with the following error messages: [...] [build CXX] vcl/unx/gtk3/gtk3fpicker.cxx /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx: In member function ‘void GtkInstanceMenuButton::toggle_menu()’: /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2893:13: error: ‘GdkSeat’ was not declared in this scope GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2893:13: note: suggested alternative: ‘GdkEvent’ GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~ GdkEvent /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2893:22: error: ‘pSeat’ was not declared in this scope GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2893:22: note: suggested alternative: ‘creat’ GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^ creat /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2893:30: error: ‘gdk_display_get_default_seat’ was not declared in this scope GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~~ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2893:30: note: suggested alternative: ‘gdk_display_get_default_screen’ GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~~ gdk_display_get_default_screen /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2894:13: error: ‘gdk_seat_ungrab’ was not declared in this scope gdk_seat_ungrab(pSeat); ^~~ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2894:13: note: suggested alternative: ‘gdk_device_ungrab’ gdk_seat_ungrab(pSeat); ^~~ gdk_device_ungrab /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2929:13: error: ‘GdkSeat’ was not declared in this scope GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2929:13: note: suggested alternative: ‘GdkEvent’ GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~ GdkEvent /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2929:22: error: ‘pSeat’ was not declared in this scope GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2929:22: note: suggested alternative: ‘creat’ GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^ creat /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2929:30: error: ‘gdk_display_get_default_seat’ was not declared in this scope GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~~ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2929:30: note: suggested alternative: ‘gdk_display_get_default_screen’ GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~~ gdk_display_get_default_screen /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2931:27: error: ‘GDK_SEAT_CAPABILITY_ALL’ was not declared in this scope GDK_SEAT_CAPABILITY_ALL, true, nullptr, nullptr, nullptr, nullptr); ^~~ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2931:27: note: suggested alternative: ‘GTK_PRINT_CAPABILITY_SCALE’ GDK_SEAT_CAPABILITY_ALL, true, nullptr, nullptr, nullptr, nullptr); ^~~ GTK_PRINT_CAPABILITY_SCALE /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2930:13: error: ‘gdk_seat_grab’ was not declared in this scope gdk_seat_grab(pSeat, gtk_widget_get_window(GTK_WIDGET(m_pMenuHack)), ^ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2930:13: note: suggested alternative: ‘gdk_device_grab’ gdk_seat_grab(pSeat, gtk_widget_get_window(GTK_WIDGET(m_pMenuHack)), ^ gdk_device_grab /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx: In member function ‘void GtkInstanceMenuButton::grab_broken(GdkEventGrabBroken*)’: /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2953:13: error: ‘GdkSeat’ was not declared in this scope GdkSeat* pSeat = gdk_display_get_default_seat(pDisplay); ^~~ /home/libo/master/vcl/unx/gtk3/gtk3gtkinst.cxx:2953:13: note: suggested
[Libreoffice-bugs] [Bug 91688] VIEWING: Print Preview does not display comments
https://bugs.documentfoundation.org/show_bug.cgi?id=91688 --- Comment #6 from Thanos --- There are the best process to create the strong password forever to help you save the all working way in system so get here http://passwordsinmicrosoftedge.com/ and choose the function for protect the version of computer. -- 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-1' - sw/uiconfig
sw/uiconfig/swriter/ui/notebookbar_compact.ui | 522 +- 1 file changed, 508 insertions(+), 14 deletions(-) New commits: commit 00b35156a3f076b0ad06c4434c263f8ac6071c5e Author: andreas kainz Date: Mon Jun 18 11:24:27 2018 +0200 NB writer: notebookbar_compact add context-printpreview tab Change-Id: Ie7ea10eeba74f07342fd47a78193d7c0193d6d40 Reviewed-on: https://gerrit.libreoffice.org/55985 Tested-by: Jenkins Reviewed-by: andreas_kainz (cherry picked from commit d5b4b002d9f60c9757e5aa971254ec824e04afc7) Reviewed-on: https://gerrit.libreoffice.org/56427 diff --git a/sw/uiconfig/swriter/ui/notebookbar_compact.ui b/sw/uiconfig/swriter/ui/notebookbar_compact.ui index 915ef138dac6..981a6ceab8e3 100644 --- a/sw/uiconfig/swriter/ui/notebookbar_compact.ui +++ b/sw/uiconfig/swriter/ui/notebookbar_compact.ui @@ -9716,6 +9716,500 @@ + +True +False + + +True +False +center +True + + +True +False +center +True + + +True +False +icons +False + + +True +False +.uno:ShowSinglePage + + +False +False + + + + +True +False +.uno:ShowTwoPages + + +False +False + + + + +True +False +.uno:ShowBookview + + +False +False + + + + +True +False +.uno:ShowMultiplePages + + +False +False + + + + +False +True +0 + + + + +True +False +5 +5 +vertical + + +False +True +5 +2 + + + + +False +True +0 + + + + +True +False +center +True + + +True +False +icons +False + + +True +False +.uno:GoToStartOfDoc + + +False +False + + + + +True +False +.uno:PageUp + + +False +
[Libreoffice-bugs] [Bug 108626] LibreOffice Writer comment boxes are too small and should be resizable
https://bugs.documentfoundation.org/show_bug.cgi?id=108626 --- Comment #4 from Thanos --- Thanks for the update here you have to access all function in way to use remote desktop to connect to a windows 10 computer just going the online here http://remotedesktopwindows10.com and save the all service here that the site given you thanks. -- 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 86725] Comments disappearing
https://bugs.documentfoundation.org/show_bug.cgi?id=86725 --- Comment #8 from Thanos --- I must be like to visit here this amazing blog you have to see here this latest function for microsoft windows 10 help support just look here http://gethelpwindows10.com and save the all update online to use easily windows system. -- 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 107728] FILESAVE: xlsx files always exported with comments shown
https://bugs.documentfoundation.org/show_bug.cgi?id=107728 --- Comment #9 from Thanos --- You can must be like to visit here this amazing blog get the function here for delete bing search history completely and visit here http://deletebinghistory.com for save the all update online forever access in commend so thanks for the update. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 60126] pdf export : comments are exported as tooltips with very narrow vertical lines to localise them
https://bugs.documentfoundation.org/show_bug.cgi?id=60126 --- Comment #9 from Thanos --- That the very nice post for to all web users you have to connect the online fix connection to bluetooth audio device and wireless display in windows get here http://fixwindows10connections.com and save the all update for communication to all users easily. -- 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: nlpsolver/src
nlpsolver/src/com/sun/star/comp/Calc/NLPSolver/BaseEvolutionarySolver.java |
6 ++
1 file changed, 6 insertions(+)
New commits:
commit 02a66f29fec36aed5fb1e800a08c1390d3674b59
Author: Julien Nabet
Date: Sun Jun 24 21:35:06 2018 +0200
tdf#43388: add missing info for Evolutionary Algorithm Solver
Add SolverConstraintOperator.INTEGER_value case and in the same time
the also missing SolverConstraintOperator.BINARY_value case
Change-Id: I18b826e74a2381dedaea3090919118b8d5dad072
Reviewed-on: https://gerrit.libreoffice.org/56359
Tested-by: Jenkins
Reviewed-by: Julien Nabet
diff --git
a/nlpsolver/src/com/sun/star/comp/Calc/NLPSolver/BaseEvolutionarySolver.java
b/nlpsolver/src/com/sun/star/comp/Calc/NLPSolver/BaseEvolutionarySolver.java
index 701e6ba63226..c0b10c2f4951 100644
--- a/nlpsolver/src/com/sun/star/comp/Calc/NLPSolver/BaseEvolutionarySolver.java
+++ b/nlpsolver/src/com/sun/star/comp/Calc/NLPSolver/BaseEvolutionarySolver.java
@@ -105,6 +105,12 @@ public abstract class BaseEvolutionarySolver extends
BaseNLPSolver {
case SolverConstraintOperator.LESS_EQUAL_value:
setDefaultYAt(i + 1, BasicBound.MINDOUBLE,
constraint.Data);
break;
+case SolverConstraintOperator.INTEGER_value:
+setDefaultYAt(i + 1, BasicBound.MINDOUBLE,
BasicBound.MAXDOUBLE);
+break;
+case SolverConstraintOperator.BINARY_value:
+setDefaultYAt(i + 1, 0, 1);
+break;
}
}
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 118280] 6.1 beta2 starts with crash on empty profile (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=118280 Akshya Kumar changed: What|Removed |Added CC||b7...@oic.jp --- Comment #8 from Akshya Kumar --- *** Bug 118387 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 118387] 6.1 beta2 starts with crash on empty profile (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=118387 Akshya Kumar changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #1 from Akshya Kumar --- *** This bug has been marked as a duplicate of bug 118280 *** -- 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 118387] New: 6.1 beta2 starts with crash on empty profile (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=118387 Bug ID: 118387 Summary: 6.1 beta2 starts with crash on empty profile (Windows) Product: LibreOffice Version: 6.0.0.0.alpha1+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: b7...@oic.jp Description: if i open the attached file with lo 6 alpha 1, the presentation starts. Steps to Reproduce: 1.open PPTS 2.open context menu 3.click "edit Presentation Actual Results: LO6 renders the WMF differently in presentation. Expected Results: It should be rendered the same. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118320] Add support for Windows 10 dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118320 V Stuart Foote changed: What|Removed |Added CC||michael.me...@collabora.com ||, mikekagan...@hotmail.com, ||tima...@gmail.com --- Comment #10 from V Stuart Foote --- (In reply to Pedro from comment #9) > ... > > This is relevant because, in Build 2018 they announced XAML islands for > legay software like win32 apps, WPF and WinForms: > > https://developer.microsoft.com/en-us/events/build/content/announcing-uwp- > xaml-islands?playlist=80d147e8-f3b0-4ca0-a96f-cfc8e80bec20 > > https://www.windowscentral.com/microsoft-giving-developers-access-fluent- > design-win32-apps-and-more That may be, but LibreOffice being cross platform we can not jump on every MS SDK twist. Do you somehow think Windows 7, Windows 8|8.1, or Windows 10 will support the XAML? I seriously doubt it... Meaning, if MS publishes a valid API for C++ development of win32 Desktop apps--only then can we adopt changes to MS theming to our internal handling of theme colors. And support all our Windows targets. This is a valid goal, but a lot remains to be seen with how MS implements. -- 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
New Defects reported by Coverity Scan for LibreOffice
Hi,
Please find the latest report on new defect(s) introduced to LibreOffice found
with Coverity Scan.
3 new defect(s) introduced to LibreOffice found with Coverity Scan.
3 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent
build analyzed by Coverity Scan.
New defect(s) Reported-by: Coverity Scan
Showing 3 of 3 defect(s)
** CID 1437527: Null pointer dereferences (FORWARD_NULL)
*** CID 1437527: Null pointer dereferences (FORWARD_NULL)
/sw/source/uibase/utlui/content.cxx: 695 in SwContentType::FillMemberList(bool
*)()
689 if(nullptr != pbLevelOrVisibilityChanged)
690 {
691 // need to check visibility (and equal entry
number) after
692 // creation due to a sorted list being used here
(before,
693 // entries with same index were compared already at
creation
694 // time what worked before a sorted list was used)
>>> CID 1437527: Null pointer dereferences (FORWARD_NULL)
>>> Passing null pointer "pOldMember" to "checkVisibilityChanged", which
>>> dereferences it.
695 *pbLevelOrVisibilityChanged =
checkVisibilityChanged(
696 *pOldMember,
697 *pMember);
698 }
699 }
700 nMemberCount = pMember->size();
** CID 1437526: Error handling issues (CHECKED_RETURN)
/sc/source/filter/excel/xipivot.cxx: 1488 in XclImpPivotTable::Convert()()
*** CID 1437526: Error handling issues (CHECKED_RETURN)
/sc/source/filter/excel/xipivot.cxx: 1488 in XclImpPivotTable::Convert()()
1482
1483 pDPObj->SetSaveData( aSaveData );
1484 pDPObj->SetSheetDesc( aDesc );
1485 pDPObj->SetOutRange( aOutRange );
1486 pDPObj->SetHeaderLayout( maPTViewEx9Info.mnGridLayout == 0 );
1487
>>> CID 1437526: Error handling issues (CHECKED_RETURN)
>>> Calling "InsertNewTable" without checking return value (as is done
>>> elsewhere 24 out of 27 times).
1488 GetDoc().GetDPCollection()->InsertNewTable(pDPObj);
1489 mpDPObj = pDPObj;
1490
1491 ApplyFieldInfo();
1492 ApplyMergeFlags(aOutRange, aSaveData);
1493 }
** CID 1209000: Error handling issues (CHECKED_RETURN)
/sc/qa/unit/ucalc_pivottable.cxx: 270 in Test::testPivotTable()()
*** CID 1209000: Error handling issues (CHECKED_RETURN)
/sc/qa/unit/ucalc_pivottable.cxx: 270 in Test::testPivotTable()()
264 printRange(m_pDoc, ScRange(nCol1, nRow1, 0, nCol2, nRow2, 0), "Data
sheet content (modified)");
265
266 // Now, create a copy of the datapilot object for the updated
table, but
267 // don't reload the cache which should force the copy to use the
old data
268 // from the cache.
269 ScDPObject* pDPObj2 = new ScDPObject(*pDPObj);
>>> CID 1209000: Error handling issues (CHECKED_RETURN)
>>> Calling "InsertNewTable" without checking return value (as is done
>>> elsewhere 24 out of 27 times).
270 pDPs->InsertNewTable(pDPObj2);
271
272 aOutRange = pDPObj2->GetOutRange();
273 pDPObj2->ClearTableData();
274 pDPObj2->Output(aOutRange.aStart);
275 {
To view the defects in Coverity Scan visit,
https://u2389337.ct.sendgrid.net/wf/click?upn=08onrYu34A-2BWcWUl-2F-2BfV0V05UPxvVjWch-2Bd2MGckcRZBnDJeNb0HijxaS4JNJPxk3kpyAm2AYqo71yXmnOxB72ibeUH-2F-2F1Lhi9AZq3dRu-2F4-3D_g-2BrHdvqzaBa155F-2F8AmPhpJzY63UzWDisJV95WUBpGhqFw1ICExHG8aMaV2EoFpyoWMum4BOPLCbZkP4ElPN2XL5LrZw5vnvCKuYPJxy8gIUr7rlwvayUt-2FCrYAUdNAECsYVNwsRTaTlzWt6WER5VQVXqk4CCYgDEjyskpCU4hJR4Ikq-2FtV7wY8p6Hb9aLkqcgXD4soOrM-2FKLkHqNcen6lUYf5hy8FgBsFCMgU7IIgA-3D
___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-bugs] [Bug 94682] VIEWING: OpenGL text rendering performance.
https://bugs.documentfoundation.org/show_bug.cgi?id=94682 Aron Budea changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118280] 6.1 beta2 starts with crash on empty profile (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=118280 Aron Budea changed: What|Removed |Added Keywords|bibisected |haveBacktrace, ||notBibisectable -- 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 117968] Google Drive Login Broken
https://bugs.documentfoundation.org/show_bug.cgi?id=117968 Akshya Kumar changed: What|Removed |Added Status|UNCONFIRMED |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 93529] [META] VCL/OpenGL rendering tracker bug for 5.0+
https://bugs.documentfoundation.org/show_bug.cgi?id=93529 V Stuart Foote changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #32 from V Stuart Foote --- back to NEW as this tracker has obviously been confirmed ;-) -- 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 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Bug 105537 depends on bug 118382, which changed state. Bug 118382 Summary: Crash with RTF paste https://bugs.documentfoundation.org/show_bug.cgi?id=118382 What|Removed |Added Status|RESOLVED|NEW 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 118382] Crash with RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=118382 Aron Budea changed: What|Removed |Added Resolution|DUPLICATE |--- Version|6.2.0.0.alpha0+ Master |6.1.0.0.alpha0+ See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=72 ||942 Crash report or||["SwPosition::~SwPosition() crash signature||"] CC||serge.k...@cib.de Status|RESOLVED|NEW --- Comment #11 from Aron Budea --- Bibisected to the following commit using repo bibisect-win32-6.1. Adding Cc: to Serge Krot, please take a look. https://cgit.freedesktop.org/libreoffice/core/commit/?id=deaa16bd24fba4a3a6b072ab2b94542a7dbd41c6 author Serge Krot 2018-01-29 12:17:06 +0100 committer Thorsten Behrens 2018-01-31 01:30:39 +0100 tdf#72942 Do not overwrite styles from the inserted doc -- 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 118361] FILEOPEN DOCX: Footnote separator Line position is wrong in RTL doc
https://bugs.documentfoundation.org/show_bug.cgi?id=118361 --- Comment #6 from Fahad Al-Saidi --- (In reply to chamfay from comment #5) > By changing "local setting" option to any arabic language, all works fine! > if you want to write an RTL document you must do that. > > Regards. thanks for the workaround but still it is a valid 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 118382] Crash with RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=118382 --- Comment #10 from Aron Budea --- Also crashes with 6.1 beta2 (x86), but not with x64 / Windows 7. Crash report: http://crashreport.libreoffice.org/stats/crash_details/48e2a1fd-9da9-4883-bf90-5b1b08e53370 -- 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 94682] VIEWING: OpenGL text rendering performance.
https://bugs.documentfoundation.org/show_bug.cgi?id=94682 Akshya Kumar changed: What|Removed |Added Status|NEW |UNCONFIRMED Component|Writer |LibreOffice 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 93529] [META] VCL/OpenGL rendering tracker bug for 5.0+
https://bugs.documentfoundation.org/show_bug.cgi?id=93529 Akshya Kumar changed: What|Removed |Added Status|NEW |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 98000] FILESAVE DOCX Problem with size of headers
https://bugs.documentfoundation.org/show_bug.cgi?id=98000 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 100524] [FILEOPEN] Spaces between page number/count fields lost on import of specific DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=100524 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 108749] Styles fail to import correctly from Word (and are utterly broken) (and caused a 1x crash)
https://bugs.documentfoundation.org/show_bug.cgi?id=108749 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 102521] Bad docx text alignment
https://bugs.documentfoundation.org/show_bug.cgi?id=102521 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 84340] FILEOPEN: DOCX - direct formatting text color not retaining
https://bugs.documentfoundation.org/show_bug.cgi?id=84340 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 74367] FILEOPEN: DOCX wrong import of page margins in specific file
https://bugs.documentfoundation.org/show_bug.cgi?id=74367 --- Comment #12 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 52365] No “Copy” option in spellcheck context menu
https://bugs.documentfoundation.org/show_bug.cgi?id=52365 --- Comment #17 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 97769] FILEOPEN DOCX Errant Line Number & Pagination Issues
https://bugs.documentfoundation.org/show_bug.cgi?id=97769 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 81567] FILESAVE: DOCX caption of image is shown at top instead of bottom in Word
https://bugs.documentfoundation.org/show_bug.cgi?id=81567 --- Comment #15 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 106233] FILEOPEN: docx table cell left spacing read incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=106233 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 92335] FILEOPEN FILESAVE: Character style for bullets added every time docx document is saved
https://bugs.documentfoundation.org/show_bug.cgi?id=92335 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 99602] subscript in character style not converted into docx
https://bugs.documentfoundation.org/show_bug.cgi?id=99602 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 54516] FILEOPEN DOCX: page breaks in otherwise empty paragraphs ignored
https://bugs.documentfoundation.org/show_bug.cgi?id=54516 --- Comment #15 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 104345] FILEOPEN DOCX: Paragraphs with top and bottom border, overlapping borders invisible
https://bugs.documentfoundation.org/show_bug.cgi?id=104345 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 94628] Fileopen: Docx custom numbering symbol incorrectly displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=94628 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 108721] CREATE TABLE: writer allows a huge number of cells without warning
https://bugs.documentfoundation.org/show_bug.cgi?id=108721 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 61063] FILEOPEN: DOCX - Textbox and its text not shown after reopening
https://bugs.documentfoundation.org/show_bug.cgi?id=61063 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 99228] Page Borders and Watermarks displayed incorrectly (WPS)
https://bugs.documentfoundation.org/show_bug.cgi?id=99228 --- Comment #5 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 95032] Border colour "clear" not retained
https://bugs.documentfoundation.org/show_bug.cgi?id=95032 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 103553] FORMATTING: Writer show zero page borders in specific docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=103553 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 102264] FILEOPEN DOCX Incorrect displaying of numbered sections
https://bugs.documentfoundation.org/show_bug.cgi?id=102264 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 108557] FILEOPEN: DOCX file numbered list has out of sequence number when opened in LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=108557 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 106572] FILEOPEN DOCX: header position becomes page margin
https://bugs.documentfoundation.org/show_bug.cgi?id=106572 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 97899] FILEOPEN: Numbering format in (part of) docx files not imported correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=97899 --- Comment #18 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 50760] If different format in cells, Standard format not applied to all of them in 1 action
https://bugs.documentfoundation.org/show_bug.cgi?id=50760 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 51605] Field add corrupts table
https://bugs.documentfoundation.org/show_bug.cgi?id=51605 --- Comment #12 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 96321] FORMATTING: in imported doc or docx, rendered underlines lines do not appear evenly spaced
https://bugs.documentfoundation.org/show_bug.cgi?id=96321 --- Comment #2 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 106174] FILEOPEN: Paragraph alignment inherited from parent style not loaded from docx file
https://bugs.documentfoundation.org/show_bug.cgi?id=106174 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 51311] FILESAVE: Writer takes a long time to begin saving large files
https://bugs.documentfoundation.org/show_bug.cgi?id=51311 --- Comment #11 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 103555] Incorrect number style. Digits instead of letters
https://bugs.documentfoundation.org/show_bug.cgi?id=103555 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 102905] Saving an odt file as OOXML gives white Area color fill to Text body paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=102905 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 32138] FORMATTING: Docx file not page-breaking the same as Office 2007
https://bugs.documentfoundation.org/show_bug.cgi?id=32138 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 98497] FILESAVE: Fonts settings inside Charts lost on DOCX export
https://bugs.documentfoundation.org/show_bug.cgi?id=98497 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 104060] FILEOPEN DOCX: Writer don't show correctly text align Text when open DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=104060 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 98498] Scatter chart on DOCX file imported from Writer loses data of first series
https://bugs.documentfoundation.org/show_bug.cgi?id=98498 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 106471] DOCX, FILESAVE: bullet size increased when saving to docx
https://bugs.documentfoundation.org/show_bug.cgi?id=106471 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 69864] VIEWING: DOCX - Cover Page not loaded
https://bugs.documentfoundation.org/show_bug.cgi?id=69864 --- Comment #8 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 85438] FILEOPEN: missing page breaks (or different page crossings due to different rendering?) in DOC file
https://bugs.documentfoundation.org/show_bug.cgi?id=85438 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 94657] borders not visible on loading docx
https://bugs.documentfoundation.org/show_bug.cgi?id=94657 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 94728] Shadow color in DOCX is different from Word
https://bugs.documentfoundation.org/show_bug.cgi?id=94728 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 53843] FORMATTING: The line spacing inside table cells does not affect the last line (causing wrong cells' height)
https://bugs.documentfoundation.org/show_bug.cgi?id=53843 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 100516] [FILEOPEN] Field Page Count (statistics) converted to number, but placed as field on wrong place on import of specific DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=100516 --- Comment #4 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 104580] FILEOPEN DOCX: Table alignment is a little bit off
https://bugs.documentfoundation.org/show_bug.cgi?id=104580 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 95027] Numbered paragraphs applied incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=95027 --- Comment #10 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 97569] Loading and saving of docx breaks lists with bulgarian, russian or serbian numbering
https://bugs.documentfoundation.org/show_bug.cgi?id=97569 --- Comment #6 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 83309] FILEOPEN: text paragraph indentation/tab stops in .DOCX displayed incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=83309 --- Comment #16 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 104703] FILEOPEN: Wrong Position of MS .docx Chart Object on Import
https://bugs.documentfoundation.org/show_bug.cgi?id=104703 --- Comment #3 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 73201] FILEOPEN: erratic DOCX page count / No warning on export of non-existing pages to PDF
https://bugs.documentfoundation.org/show_bug.cgi?id=73201 --- Comment #7 from QA Administrators --- ** Please read this message in its entirety before responding ** 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 118280] 6.1 beta2 starts with crash on empty profile (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=118280 Akshya Kumar changed: What|Removed |Added Severity|critical|normal Keywords||bibisected --- Comment #7 from Akshya Kumar --- i tried to resolve the issue but.. -- 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-1' - helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 5b7741075fd174efbe0b04ca21b5da5cbc12c034 Author: Olivier Hallot Date: Sun Jun 24 23:02:18 2018 -0300 Updated core Project: help f1c36059ee708b31289ff1f782df64fb18bd6d1c Fill help page for writer Style menu Fix XML Change-Id: I0d8d362774eecd200a6510dfecfe089274ae631d Reviewed-on: https://gerrit.libreoffice.org/56368 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 7b4770831a82..f1c36059ee70 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 7b4770831a82435bee3765f130dadc848e7efb70 +Subproject commit f1c36059ee708b31289ff1f782df64fb18bd6d1c ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-commits] help.git: AllLangHelp_swriter.mk source/text
AllLangHelp_swriter.mk|1 + source/text/shared/00/00040500.xhp|1 + source/text/swriter/00/stylesmenu.xhp | 25 + source/text/swriter/guide/load_styles.xhp | 27 +++ source/text/swriter/main0115.xhp | 20 +++- 5 files changed, 57 insertions(+), 17 deletions(-) New commits: commit 0dad33c002dc2308100e0d315ed16c527cdb5061 Author: Olivier Hallot Date: Sun Jun 24 23:02:18 2018 -0300 Fill help page for writer Style menu Fix XML Change-Id: I0d8d362774eecd200a6510dfecfe089274ae631d Reviewed-on: https://gerrit.libreoffice.org/56367 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/AllLangHelp_swriter.mk b/AllLangHelp_swriter.mk index c7c771472..ba34e1582 100644 --- a/AllLangHelp_swriter.mk +++ b/AllLangHelp_swriter.mk @@ -24,6 +24,7 @@ $(eval $(call gb_AllLangHelp_add_helpfiles,swriter,\ helpcontent2/source/text/swriter/00/0404 \ helpcontent2/source/text/swriter/00/0405 \ helpcontent2/source/text/swriter/00/0406 \ +helpcontent2/source/text/swriter/00/stylesmenu \ helpcontent2/source/text/swriter/01/0112 \ helpcontent2/source/text/swriter/01/0115 \ helpcontent2/source/text/swriter/01/01160100 \ diff --git a/source/text/shared/00/00040500.xhp b/source/text/shared/00/00040500.xhp index 8194f1135..ac48def40 100644 --- a/source/text/shared/00/00040500.xhp +++ b/source/text/shared/00/00040500.xhp @@ -196,6 +196,7 @@ + Choose View - Styles Command+T F11 diff --git a/source/text/swriter/00/stylesmenu.xhp b/source/text/swriter/00/stylesmenu.xhp new file mode 100644 index 0..781e56275 --- /dev/null +++ b/source/text/swriter/00/stylesmenu.xhp @@ -0,0 +1,25 @@ + + + + + + +The styles menu +/text/swriter/00/stylesmenu.xhp + + + +Choose Styles - Edit Styles. +Choose Styles - Update Style or CommandCtrl+ Shift + F11. +Choose Styles - New Style or Shift + F11. +Choose Styles - Load Styles. +Choose Styles - Manage Styles or F11. + + diff --git a/source/text/swriter/guide/load_styles.xhp b/source/text/swriter/guide/load_styles.xhp index 53c714cc0..4d12f4ff8 100644 --- a/source/text/swriter/guide/load_styles.xhp +++ b/source/text/swriter/guide/load_styles.xhp @@ -35,17 +35,20 @@ Using Styles From Another Document or Template You can import styles from another document or template into the current document. - - -Choose View - Styles to open the Styles sidebar deck. - - -Click the arrow next to the New Style from Selection icon to open the submenu. - - -Choose Load styles. - - + Open the Load Styles dialog box by either + + + Choose View - Styles or + + + to open the Styles sidebar deck. + + + Click the arrow next to the New Style from Selection icon to open the submenu. + + + + Use the check boxes at the bottom of the dialog to select the style types that you want to import. To replace styles in the current document that have the same name as the ones you are importing, select Overwrite. @@ -67,4 +70,4 @@ - \ No newline at end of file + diff --git a/source/text/swriter/main0115.xhp b/source/text/swriter/main0115.xhp index 9f5c385d1..e10269b54 100644 --- a/source/text/swriter/main0115.xhp +++ b/source/text/swriter/main0115.xhp @@ -19,7 +19,7 @@ --> - + Styles /text/swriter/main0115.xhp @@ -28,10 +28,20 @@ Styles - Contains commands to set, create, edit, update, load, and manage styles in a text document. + Contains commands to apply, create, edit, update, load, and manage styles in a text document. - Default - Set the current paragraph or selected paragraphs to the default style. + Text styles entries + The entries includes most common paragraph, character and list styles. Click on the style to apply. + You can customize the list of styles entries using menu Tools - Customize. Because custom styles belongs to the actual document, remember to store the customized menu in the document scope. + Edit Style + Opens the Paragraph Style dialog box of the current paragraph. + Update Style + Update the paragraph style with the direct formatting applied to the current paragraph. + New style + Adds a paragraph style with the settings of the current selection. You will be prompted to enter the style name. + Load Styles + Import styles from another document or template into the current document. + Manage Styles + Opens the Styles deck in the sidebar. -
[Libreoffice-commits] help.git: Branch 'libreoffice-6-1' - AllLangHelp_swriter.mk source/text
AllLangHelp_swriter.mk|1 + source/text/shared/00/00040500.xhp|1 + source/text/swriter/00/stylesmenu.xhp | 25 + source/text/swriter/guide/load_styles.xhp | 27 +++ source/text/swriter/main0115.xhp | 20 +++- 5 files changed, 57 insertions(+), 17 deletions(-) New commits: commit f1c36059ee708b31289ff1f782df64fb18bd6d1c Author: Olivier Hallot Date: Sun Jun 24 23:02:18 2018 -0300 Fill help page for writer Style menu Fix XML Change-Id: I0d8d362774eecd200a6510dfecfe089274ae631d Reviewed-on: https://gerrit.libreoffice.org/56368 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/AllLangHelp_swriter.mk b/AllLangHelp_swriter.mk index c7c771472..ba34e1582 100644 --- a/AllLangHelp_swriter.mk +++ b/AllLangHelp_swriter.mk @@ -24,6 +24,7 @@ $(eval $(call gb_AllLangHelp_add_helpfiles,swriter,\ helpcontent2/source/text/swriter/00/0404 \ helpcontent2/source/text/swriter/00/0405 \ helpcontent2/source/text/swriter/00/0406 \ +helpcontent2/source/text/swriter/00/stylesmenu \ helpcontent2/source/text/swriter/01/0112 \ helpcontent2/source/text/swriter/01/0115 \ helpcontent2/source/text/swriter/01/01160100 \ diff --git a/source/text/shared/00/00040500.xhp b/source/text/shared/00/00040500.xhp index 8194f1135..ac48def40 100644 --- a/source/text/shared/00/00040500.xhp +++ b/source/text/shared/00/00040500.xhp @@ -196,6 +196,7 @@ + Choose View - Styles Command+T F11 diff --git a/source/text/swriter/00/stylesmenu.xhp b/source/text/swriter/00/stylesmenu.xhp new file mode 100644 index 0..781e56275 --- /dev/null +++ b/source/text/swriter/00/stylesmenu.xhp @@ -0,0 +1,25 @@ + + + + + + +The styles menu +/text/swriter/00/stylesmenu.xhp + + + +Choose Styles - Edit Styles. +Choose Styles - Update Style or CommandCtrl+ Shift + F11. +Choose Styles - New Style or Shift + F11. +Choose Styles - Load Styles. +Choose Styles - Manage Styles or F11. + + diff --git a/source/text/swriter/guide/load_styles.xhp b/source/text/swriter/guide/load_styles.xhp index 53c714cc0..4d12f4ff8 100644 --- a/source/text/swriter/guide/load_styles.xhp +++ b/source/text/swriter/guide/load_styles.xhp @@ -35,17 +35,20 @@ Using Styles From Another Document or Template You can import styles from another document or template into the current document. - - -Choose View - Styles to open the Styles sidebar deck. - - -Click the arrow next to the New Style from Selection icon to open the submenu. - - -Choose Load styles. - - + Open the Load Styles dialog box by either + + + Choose View - Styles or + + + to open the Styles sidebar deck. + + + Click the arrow next to the New Style from Selection icon to open the submenu. + + + + Use the check boxes at the bottom of the dialog to select the style types that you want to import. To replace styles in the current document that have the same name as the ones you are importing, select Overwrite. @@ -67,4 +70,4 @@ - \ No newline at end of file + diff --git a/source/text/swriter/main0115.xhp b/source/text/swriter/main0115.xhp index 9f5c385d1..e10269b54 100644 --- a/source/text/swriter/main0115.xhp +++ b/source/text/swriter/main0115.xhp @@ -19,7 +19,7 @@ --> - + Styles /text/swriter/main0115.xhp @@ -28,10 +28,20 @@ Styles - Contains commands to set, create, edit, update, load, and manage styles in a text document. + Contains commands to apply, create, edit, update, load, and manage styles in a text document. - Default - Set the current paragraph or selected paragraphs to the default style. + Text styles entries + The entries includes most common paragraph, character and list styles. Click on the style to apply. + You can customize the list of styles entries using menu Tools - Customize. Because custom styles belongs to the actual document, remember to store the customized menu in the document scope. + Edit Style + Opens the Paragraph Style dialog box of the current paragraph. + Update Style + Update the paragraph style with the direct formatting applied to the current paragraph. + New style + Adds a paragraph style with the settings of the current selection. You will be prompted to enter the style name. + Load Styles + Import styles from another document or template into the current document. + Manage Styles + Opens the Styles deck in the sidebar. -
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 757d9e43315755869af30e79c0457fd529cb050a Author: Olivier Hallot Date: Sun Jun 24 23:02:18 2018 -0300 Updated core Project: help 0dad33c002dc2308100e0d315ed16c527cdb5061 Fill help page for writer Style menu Fix XML Change-Id: I0d8d362774eecd200a6510dfecfe089274ae631d Reviewed-on: https://gerrit.libreoffice.org/56367 Tested-by: Jenkins Reviewed-by: Olivier Hallot diff --git a/helpcontent2 b/helpcontent2 index 971f4369e976..0dad33c002dc 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit 971f4369e9763903aaa6801618040c44b4bbf1b0 +Subproject commit 0dad33c002dc2308100e0d315ed16c527cdb5061 ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
GSOC 100 paper cuts update
Hi everyone, I have been working on tdf#36867 - Not currently possible to undo wrong capitalisation in Calc. I have been making the changes suggested by Eike Rathe. https://gerrit.libreoffice.org/#/c/55820/ I have also been working on tdf#51223 - Cannot undo auto-capitalise with enter. Now, the AutoCorrect happens after you enter a new line as part of AutoFormat. https://gerrit.libreoffice.org/#/c/56267/ I have also created a wiki article where you can view the current paper cuts that have not been completed. https://wiki.documentfoundation.org/100_Paper_Cuts Thanks, Nickson ___ LibreOffice mailing list LibreOffice@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice
[Libreoffice-ux-advise] [Bug 118355] Menu Styles miss "Body Text" entry in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=118355 --- Comment #7 from Kenneth Hanson --- I think the biggest reason to have both Text Body and Default Paragraph in the menu is as a hint for users that are not familiar with styles. It makes it clear that these are different, and shows their keyboard shortcuts: Ctrl+1/2/3 for headings, Ctrl+0 for body text, Ctrl+Shift+0 for Default Paragraph. Such users can easily use the menu until they learn the shortcuts. Text Body is the primary paragraph style, the level below all headings. Default Paragraph is occasionally comes in handy when you need to get rid of spacing/indentation on a one-time basis (and there is no logical name or urgent need for a new style that changes nothing from the default). The paradigm is easy to understand when presented like this. The extra keyboard modifier for Default Paragraph makes it obvious that this is not the "normal" style. That being said, bug 47295 really does need to be fixed. I've made this change in my default template long ago, so I didn't realize it hadn't been fixed yet. The fact that Text Body is also for all practical purposes a "reset" switch for paragraph style is yet another reason to include it, but it's not the main reason. I contrast, I would oppose adding most other styles because they don't match the above reasoning. They are not part of the heading paradigm, don't (?) have default keyboard shortcuts, and are not critical for all documents. -- 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 118355] Menu Styles miss "Body Text" entry in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=118355 --- Comment #7 from Kenneth Hanson --- I think the biggest reason to have both Text Body and Default Paragraph in the menu is as a hint for users that are not familiar with styles. It makes it clear that these are different, and shows their keyboard shortcuts: Ctrl+1/2/3 for headings, Ctrl+0 for body text, Ctrl+Shift+0 for Default Paragraph. Such users can easily use the menu until they learn the shortcuts. Text Body is the primary paragraph style, the level below all headings. Default Paragraph is occasionally comes in handy when you need to get rid of spacing/indentation on a one-time basis (and there is no logical name or urgent need for a new style that changes nothing from the default). The paradigm is easy to understand when presented like this. The extra keyboard modifier for Default Paragraph makes it obvious that this is not the "normal" style. That being said, bug 47295 really does need to be fixed. I've made this change in my default template long ago, so I didn't realize it hadn't been fixed yet. The fact that Text Body is also for all practical purposes a "reset" switch for paragraph style is yet another reason to include it, but it's not the main reason. I contrast, I would oppose adding most other styles because they don't match the above reasoning. They are not part of the heading paradigm, don't (?) have default keyboard shortcuts, and are not critical for all documents. -- 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 118386] New: Closing last document closes LibreOffice
https://bugs.documentfoundation.org/show_bug.cgi?id=118386 Bug ID: 118386 Summary: Closing last document closes LibreOffice Product: LibreOffice Version: 6.0.5.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Lately (cannot tell exactly which version; I attribute this to 6.0 line), when I close the last document open in LibreOffice (using a small cross in the right of menu bar, or File->Close), closes whole LibreOffice (while the expected behaviour is to return to Start Center). The currently-visible behaviour must only happen when using File->Exit LibreOffice, or the main closing cross in the title bar. Tested with Version: 6.0.5.2 (x64) Build ID: 54c8cbb85f300ac59db32fe8a675ff7683cd5a16 CPU threads: 4; OS: Windows 10.0; UI render: default; Locale: en-GB (ru_RU); Calc: CL -- 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 118217] Menubar: writer menubar update
https://bugs.documentfoundation.org/show_bug.cgi?id=118217 --- Comment #4 from Heiko Tietze --- And now please answer the Why. And please in a way that we can point a user who is missing a particular command to the explanation why it needed to be changed. Meaning every single change needs a traceable reasoning. Furthermore, have you checked your modifications against the guideline? https://wiki.documentfoundation.org/Design/MenuBar -- 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 118385] LibreOffice Writer unexpectedly silently exits on loading a certain document.
https://bugs.documentfoundation.org/show_bug.cgi?id=118385 --- Comment #3 from himajin100...@gmail.com --- info:sax.fastparser:10656:20016:sax/source/fastparser/fastparser.cxx:1230: startElement line 2 column 117973 w:ins info:sax.fastparser:10656:20016:sax/source/fastparser/fastparser.cxx:1230: startElement line 2 column 117978 w:r (snip) info:vcl.gdi.wndproc:10656:20016:vcl/win/app/salinst.cxx:585: SalComWndProc(nMsg=1138, wParam=138, lParam=6098430) info:vcl.gdi.wndproc:10656:20016:vcl/win/window/salframe.cxx:5440: SalFrameWndProc(nMsg=130, wParam=0, lParam=0) warn:vcl:10656:20016:vcl/win/window/salframe.cxx:434: CreateWindowExW failed: ハンドルが無効です。 warn:vcl.window:10656:20016:vcl/source/window/window.cxx:551: Window 0273DB1BBC40 marked as frame window, is missing from -- 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 118385] LibreOffice Writer unexpectedly silently exits on loading a certain document.
https://bugs.documentfoundation.org/show_bug.cgi?id=118385 --- Comment #2 from himajin100...@gmail.com --- Created attachment 143121 --> https://bugs.documentfoundation.org/attachment.cgi?id=143121=edit non-reproducible document, may be helpful -- 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 118385] LibreOffice Writer unexpectedly silently exits on loading a certain document.
https://bugs.documentfoundation.org/show_bug.cgi?id=118385 himajin100...@gmail.com changed: What|Removed |Added CC||himajin100...@gmail.com --- Comment #1 from himajin100...@gmail.com --- Created attachment 143120 --> https://bugs.documentfoundation.org/attachment.cgi?id=143120=edit reproducible document -- 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 118385] New: LibreOffice Writer unexpectedly silently exits on loading a certain document.
https://bugs.documentfoundation.org/show_bug.cgi?id=118385 Bug ID: 118385 Summary: LibreOffice Writer unexpectedly silently exits on loading a certain document. Product: LibreOffice Version: 6.2.0.0.alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: himajin100...@gmail.com Description: the following message may be useful. info:sax.fastparser:10656:20016:sax/source/fastparser/fastparser.cxx:1230: startElement line 2 column 117898 v:stroke warn:legacy.osl:10656:20016:oox/source/vml/vmlshapecontainer.cxx:45: lclMapShapesById - shape identifier already used info:vcl.virdev:10656:20016:vcl/source/gdi/virdev.cxx:204: VirtualDevice::VirtualDevice( 0 ) info:vcl.virdev:10656:20016:vcl/source/gdi/virdev.cxx:112: ImplInitVirDev(0,0,0) warn:vcl:10656:20016:vcl/win/gdi/salvd.cxx:112: CreateCompatibleDC failed: パラメーターが間違っています。 warn:vcl:10656:20016:vcl/win/gdi/salvd.cxx:67: CreateDIBSection failed: パラメーターが間違っています。 warn:sax:10656:20016:sax/source/fastparser/fastparser.cxx:618: Unexpected exception from XML parser class com::sun::star::uno::Exception msg: Could not create system bitmap! = "パラメーターが間違っています。" is Japanese translation of "Parameter is not valid" Steps to Reproduce: 1. try to open the attached document 2. wait for a while. Actual Results: Somehow LibreOffice exits silently Expected Results: LibreOffice successfully displays the document Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118381] Inaccurate symbol signs
https://bugs.documentfoundation.org/show_bug.cgi?id=118381 Thorsten Wagner changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |thorsten.wagne...@gmail.com |desktop.org | -- 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 118381] Inaccurate symbol signs
https://bugs.documentfoundation.org/show_bug.cgi?id=118381 --- Comment #7 from Thorsten Wagner --- The left arrow shown in screenshot 4 can be seen in Writer/Tools/Customize dialog. Patch has been submitted to Gerrit. -- 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 118382] Crash with RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=118382 --- Comment #9 from Xisco Faulí --- (In reply to Telesto from comment #8) > @Xisco Faille > Is this really a dupe of bug 117749? Of course, when interpreting it as > comment 5. However, de crash happens when pasting, without the undo part. BT > differs to Just to be sure, have you cleaned your profile? I can't reproduce it in Version: 6.2.0.0.alpha0+ Build ID: b047ae6e5bde4a20a9ad8b7d570d93496187 CPU threads: 16; OS: Windows 6.3; UI render: default; Locale: en-GB (en_GB); Calc: group threaded -- You are receiving this mail because: You are the assignee for the bug.___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 118335] Writer's Groupedbar. Wrong name of item Print preview in drop-down menu File
https://bugs.documentfoundation.org/show_bug.cgi?id=118335 --- Comment #3 from Maxim Monastirsky --- (In reply to andreas_k from comment #2) > it look like NB use PopupLabel how can I change the behavior that NB use the > default name? You can try this (didn't test, but it should work): 1) Extract the "Close Preview" string to a new command like this: Close Preview .uno:PrintPreview 1 2) Link the menu icon of .uno:ClosePrintPreview to .uno:PrintPreview in various links.txt files. 3) Change the various sw/uiconfig/*/popupmenu/preview.xml to use .uno:ClosePrintPreview instead of .uno:PrintPreview. (and test it to make sure it still works). 4) Remove the PopupLabel of .uno:PrintPreview. -- 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-1' - sysui/desktop
sysui/desktop/icons/base_app.icns|binary sysui/desktop/icons/calc_app.icns|binary sysui/desktop/icons/database.icns|binary sysui/desktop/icons/draw_app.icns|binary sysui/desktop/icons/drawing.icns |binary sysui/desktop/icons/drawing_template.icns|binary sysui/desktop/icons/empty-document.icns |binary sysui/desktop/icons/empty-template.icns |binary sysui/desktop/icons/formula.icns |binary sysui/desktop/icons/impress_app.icns |binary sysui/desktop/icons/master-document.icns |binary sysui/desktop/icons/oasis-database.icns |binary sysui/desktop/icons/oasis-drawing-template.icns |binary sysui/desktop/icons/oasis-drawing.icns |binary sysui/desktop/icons/oasis-empty-document.icns|binary sysui/desktop/icons/oasis-empty-template.icns|binary sysui/desktop/icons/oasis-formula.icns |binary sysui/desktop/icons/oasis-master-document.icns |binary sysui/desktop/icons/oasis-presentation-template.icns |binary sysui/desktop/icons/oasis-presentation.icns |binary sysui/desktop/icons/oasis-spreadsheet-template.icns |binary sysui/desktop/icons/oasis-spreadsheet.icns |binary sysui/desktop/icons/oasis-text-template.icns |binary sysui/desktop/icons/oasis-text.icns |binary sysui/desktop/icons/oasis-web-template.icns |binary sysui/desktop/icons/open.icns|binary sysui/desktop/icons/oxt-extension.icns |binary sysui/desktop/icons/presentation-template.icns |binary sysui/desktop/icons/presentation.icns|binary sysui/desktop/icons/soffice.icns |binary sysui/desktop/icons/spreadsheet-template.icns|binary sysui/desktop/icons/spreadsheet.icns |binary sysui/desktop/icons/text-template.icns |binary sysui/desktop/icons/text.icns|binary sysui/desktop/icons/web-template.icns|binary sysui/desktop/icons/writer_app.icns |binary 36 files changed New commits: commit 2d57315c11288dbdf0f119b500a5daf3dfde799a Author: andreas kainz Date: Wed Jun 20 22:01:52 2018 +0200 update app icns icons thanks Mike Saunders Change-Id: I7d358a4ccebc008efc67874db5d3f05efc80444a Reviewed-on: https://gerrit.libreoffice.org/56207 Tested-by: Jenkins Reviewed-by: andreas_kainz (cherry picked from commit dbcccd374e511f1667e09b5aade617d78f51eab5) Reviewed-on: https://gerrit.libreoffice.org/56419 diff --git a/sysui/desktop/icons/base_app.icns b/sysui/desktop/icons/base_app.icns new file mode 100644 index ..6f2ed27978ba Binary files /dev/null and b/sysui/desktop/icons/base_app.icns differ diff --git a/sysui/desktop/icons/calc_app.icns b/sysui/desktop/icons/calc_app.icns new file mode 100644 index ..28a548448f71 Binary files /dev/null and b/sysui/desktop/icons/calc_app.icns differ diff --git a/sysui/desktop/icons/database.icns b/sysui/desktop/icons/database.icns index 9fa0bbf3ed67..26a915a03119 100644 Binary files a/sysui/desktop/icons/database.icns and b/sysui/desktop/icons/database.icns differ diff --git a/sysui/desktop/icons/draw_app.icns b/sysui/desktop/icons/draw_app.icns new file mode 100644 index ..607ac35bd3a1 Binary files /dev/null and b/sysui/desktop/icons/draw_app.icns differ diff --git a/sysui/desktop/icons/drawing.icns b/sysui/desktop/icons/drawing.icns index d179d041a6ca..9890e2e3f3a7 100644 Binary files a/sysui/desktop/icons/drawing.icns and b/sysui/desktop/icons/drawing.icns differ diff --git a/sysui/desktop/icons/drawing_template.icns b/sysui/desktop/icons/drawing_template.icns new file mode 100644 index ..c884e49a0a54 Binary files /dev/null and b/sysui/desktop/icons/drawing_template.icns differ diff --git a/sysui/desktop/icons/empty-document.icns b/sysui/desktop/icons/empty-document.icns index c5c80a01e799..5d07e751f002 100644 Binary files a/sysui/desktop/icons/empty-document.icns and b/sysui/desktop/icons/empty-document.icns differ diff --git a/sysui/desktop/icons/empty-template.icns b/sysui/desktop/icons/empty-template.icns index c5c80a01e799..5d07e751f002 100644 Binary files a/sysui/desktop/icons/empty-template.icns and b/sysui/desktop/icons/empty-template.icns differ diff --git a/sysui/desktop/icons/formula.icns b/sysui/desktop/icons/formula.icns index f6dc588095f4..ecad3d13e803 100644 Binary files a/sysui/desktop/icons/formula.icns and b/sysui/desktop/icons/formula.icns differ diff --git a/sysui/desktop/icons/impress_app.icns b/sysui/desktop/icons/impress_app.icns new file mode 100644 index ..e7b0cf53abfb Binary files /dev/null and b/sysui/desktop/icons/impress_app.icns differ diff --git
[Libreoffice-commits] core.git: download.lst
download.lst |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) New commits: commit e90b7ebe137c638523923d7d2fe8bb8d8a8d75cc Author: Eike Rathke Date: Mon Jun 25 20:30:42 2018 +0200 Upgrade to language-subtag-registry-2018-04-23 Change-Id: I4b862f767db3aabfa7a62ea1c97c34279d34cce7 Reviewed-on: https://gerrit.libreoffice.org/56413 Reviewed-by: Eike Rathke Tested-by: Jenkins diff --git a/download.lst b/download.lst index 1c9a11cf95ab..d8fb26541253 100644 --- a/download.lst +++ b/download.lst @@ -130,8 +130,8 @@ export JFREEREPORT_SAC_SHA256SUM := 085f2112c51fa8c1783fac12fbd45265059641512134 export JFREEREPORT_SAC_TARBALL := 39bb3fcea1514f1369fcfc87542390fd-sacjava-1.3.zip export LIBJPEG_TURBO_SHA256SUM := 9098943b270388727ae61de82adec73cf9f0dbb240b3bc8b172595ebf405b528 export LIBJPEG_TURBO_TARBALL := libjpeg-turbo-1.5.2.tar.gz -export LANGTAGREG_SHA256SUM := b7ad618b7db518155f00490a11b861496864f18b23b4b537eb80bfe84ca6f854 -export LANGTAGREG_TARBALL := language-subtag-registry-2018-03-30.tar.bz2 +export LANGTAGREG_SHA256SUM := 14c21f4533ca74e3af9e09184d6756a750d0cd46099015ba8c595e48499aa878 +export LANGTAGREG_TARBALL := language-subtag-registry-2018-04-23.tar.bz2 export LANGUAGETOOL_SHA256SUM := 48c87e41636783bba438b65fd895821e369ed139e1465fac654323ad93c5a82d export LANGUAGETOOL_TARBALL := b63e6340a02ff1cacfeadb2c42286161-JLanguageTool-1.7.0.tar.bz2 export LCMS2_SHA256SUM := 66d02b229d2ea9474e62c2b6cd6720fde946155cd1d0d2bffdab829790a0fb22 ___ Libreoffice-commits mailing list libreoffice-comm...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 118384] New: Sidebar: Style is not added back to hierarchy after deleting and redoing it
https://bugs.documentfoundation.org/show_bug.cgi?id=118384 Bug ID: 118384 Summary: Sidebar: Style is not added back to hierarchy after deleting and redoing it Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: xiscofa...@libreoffice.org Steps to reproduce: 1. Open Writer 2. Go to Sidebar - Styles and make sure Hierarchical is choosen 3. right click on a style - new -> a new style is added a a child 4. Undo the action using Ctrl + Z -> the issue with the undo icon is covered by bug 47807 5. Redo the action -> the style is added to the bottom of the list instead of as a child as before. Reproduced in Version: 6.2.0.0.alpha0+ Build ID: dbfa1c452fd9d02330cb3ec5bf2fd4f2c7782d1a CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); Calc: group threaded and LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 -- 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 118382] Crash with RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=118382 --- Comment #8 from Telesto --- @Xisco Faille Is this really a dupe of bug 117749? Of course, when interpreting it as comment 5. However, de crash happens when pasting, without the undo part. BT differs to -- 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: desktop/scripts svx/source
desktop/scripts/soffice.sh |7 ++-
desktop/scripts/unopkg.sh |6 +-
svx/source/gengal/gengal.sh |6 +-
3 files changed, 16 insertions(+), 3 deletions(-)
New commits:
commit 8db53bfd74e48f60e3002b2ae5f7f13c9387725a
Author: Thomas Klausner
Date: Mon Jun 25 23:42:44 2018 +0200
Fix "javaPathHelper: not found" errors during startup.
javaPathHelper is a tool from OpenBSD ports, so there is no point
looking for it on other operating systems.
Change-Id: I763d717fdf7172b412d527fcd88347b2e54a8fe9
diff --git a/desktop/scripts/soffice.sh b/desktop/scripts/soffice.sh
index 5c76b6e2211d..df295cb76250 100755
--- a/desktop/scripts/soffice.sh
+++ b/desktop/scripts/soffice.sh
@@ -141,7 +141,7 @@ if echo "$checks" | grep -q "cc" ; then
fi
case "$(uname -s)" in
-NetBSD|OpenBSD|DragonFly)
+OpenBSD)
# this is a temporary hack until we can live with the default search paths
LD_LIBRARY_PATH="$sd_prog${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
JAVA_HOME=$(javaPathHelper -h libreoffice-java 2> /dev/null)
@@ -150,6 +150,11 @@ NetBSD|OpenBSD|DragonFly)
export JAVA_HOME
fi
;;
+NetBSD|DragonFly)
+# this is a temporary hack until we can live with the default search paths
+LD_LIBRARY_PATH="$sd_prog${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"
+export LD_LIBRARY_PATH
+;;
AIX)
LIBPATH="$sd_prog${LIBPATH:+:$LIBPATH}"
export LIBPATH
diff --git a/desktop/scripts/unopkg.sh b/desktop/scripts/unopkg.sh
index 83068d29d35e..3adf69c2e56e 100755
--- a/desktop/scripts/unopkg.sh
+++ b/desktop/scripts/unopkg.sh
@@ -37,7 +37,7 @@ cd "$sd_cwd" || exit $?
# this is a temporary hack until we can live with the default search paths
case "$(uname -s)" in
-NetBSD|OpenBSD|FreeBSD|DragonFly)
+OpenBSD)
LD_LIBRARY_PATH="$sd_prog${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}"
JAVA_HOME=$(javaPathHelper -h libreoffice-java 2> /dev/null)
export LD_LIBRARY_PATH
@@ -45,6 +45,10 @@ NetBSD|OpenBSD|FreeBSD|DragonFly)
export JAVA_HOME
fi
;;
+NetBSD|FreeBSD|DragonFly)
+LD_LIBRARY_PATH="$sd_prog${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}"
+export LD_LIBRARY_PATH
+;;
AIX)
LIBPATH="$sd_prog${LIBPATH:+:${LIBPATH}}"
export LIBPATH
diff --git a/svx/source/gengal/gengal.sh b/svx/source/gengal/gengal.sh
index b4d10458650a..3970ab1fa9c8 100755
--- a/svx/source/gengal/gengal.sh
+++ b/svx/source/gengal/gengal.sh
@@ -35,7 +35,7 @@ cd "$sd_cwd"
# this is a temporary hack until we can live with the default search paths
case "$(uname -s)" in
-NetBSD|OpenBSD|FreeBSD|DragonFly)
+OpenBSD)
LD_LIBRARY_PATH=$sd_prog${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
JAVA_HOME=$(javaPathHelper -h libreoffice-java 2> /dev/null)
export LD_LIBRARY_PATH
@@ -43,6 +43,10 @@ NetBSD|OpenBSD|FreeBSD|DragonFly)
export JAVA_HOME
fi
;;
+NetBSD|FreeBSD|DragonFly)
+LD_LIBRARY_PATH=$sd_prog${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
+export LD_LIBRARY_PATH
+;;
AIX)
LIBPATH=$sd_prog${LIBPATH:+:${LIBPATH}}
export LIBPATH
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
[Libreoffice-bugs] [Bug 117749] Crash when undoing the pasting of a table
https://bugs.documentfoundation.org/show_bug.cgi?id=117749 --- Comment #3 from Xisco Faulí --- *** Bug 118382 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 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Bug 105537 depends on bug 118382, which changed state. Bug 118382 Summary: Crash with RTF paste https://bugs.documentfoundation.org/show_bug.cgi?id=118382 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 118382] Crash with RTF paste
https://bugs.documentfoundation.org/show_bug.cgi?id=118382 Xisco Faulí changed: What|Removed |Added Status|NEW |RESOLVED Keywords||bibisected, bisected, ||regression OS|Windows (All) |All Resolution|--- |DUPLICATE --- Comment #7 from Xisco Faulí --- Regression introduced by https://cgit.freedesktop.org/libreoffice/core/commit/?id=83243003b46dfb258c2b41049b0e1cb82a2d7ddb, which is the same as in bug 117749 *** This bug has been marked as a duplicate of bug 117749 *** -- 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 118335] Writer's Groupedbar. Wrong name of item Print preview in drop-down menu File
https://bugs.documentfoundation.org/show_bug.cgi?id=118335 --- Comment #2 from andreas_k --- GenericCommands.xcu Print Pr~eview Toggle Print Preview Close Preview 9 it look like NB use PopupLabel how can I change the behavior that NB use the default name? -- 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
