[Bug 160913] Freeze pasting complex table inside complex table in multipage view
https://bugs.documentfoundation.org/show_bug.cgi?id=160913 --- Comment #3 from Rainer Bielefeld Retired --- c1) Bug 160303 - Table layout loop in complex table structure after paste RTF: NOT reproducible vor me with Installation of Version: 7.6.4.1 (X86_64) Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: Locale: de-DE (de_DE); UI: de-DE; Theme: Automatic (Colibre) Calc: CL threaded – Normal User Profile Skia on/of does not matter So this one might be concerning something different from Bug 160303 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160913] Freeze pasting complex table inside complex table in multipage view
https://bugs.documentfoundation.org/show_bug.cgi?id=160913 Rainer Bielefeld Retired changed: What|Removed |Added OS|All |Windows (All) Version|24.8.0.0 alpha0+ Master |7.6.4.1 release CC||LibreOffice@bielefeldundbus ||s.de --- Comment #2 from Rainer Bielefeld Retired --- For me already REPRODUCIBLE with Installation of Version: 7.6.4.1 (X86_64) Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: Locale: de-DE (de_DE); UI: de-DE; Theme: Automatic (Colibre) Calc: CL threaded – Normal User Profile Additional Info: a) Does not matter whether Skia is aktive or not. b) Currently here only confirmed with WIN c) DUP: some more observations required -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135538] Search-Replace: Regular Expression engine fails on zero length matches
https://bugs.documentfoundation.org/show_bug.cgi?id=135538 --- Comment #17 from Mike Kaganski --- A code pointer: TextSearch::RESrchFrwrd [1] uses a loop "until there is a valid match", which is not ended for a valid zero-length match. It must be investigated, why these matches are ignored. [1] https://opengrok.libreoffice.org/xref/core/i18npool/source/search/textsearch.cxx?r=6182f236#922 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160918] New: FORMCONTROLS: Add ability to sort tab order by alphanumeric based on form control name
https://bugs.documentfoundation.org/show_bug.cgi?id=160918 Bug ID: 160918 Summary: FORMCONTROLS: Add ability to sort tab order by alphanumeric based on form control name Product: LibreOffice Version: 7.5.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: st...@nyhof.id.au This is a feature request to sort the form controls tab order alphanumerically based on control name. The 'Automatic Sort' option in the form control properties tab order dialog is useful in many circumstances. However, there are times when it is not perfect. Citing two examples: 1. A checkbox or radio button might be before (i.e. to the left of) an associated text box. If it is smaller in height, the text box will be sorted first, even though a user would logically want it second. 2. Some forms use column layouts. For usability, the tab order should scroll down the first column before moving to the next column. Because 'Automatic Sort' does not recognize columns, it produces a tab order that jumps back and forth between the column based the field's vertical alignment. I do not propose to change 'Automatic Sort' to cater for these unique circumstances; it would likely be too difficult to come up with consistently effective rules. Instead, I propose that the form designer would benefit from using a naming scheme with their controls that alphanumerically sequences their tab order (e.g. 1.1, 1.2, 1.2.1, etc.). Then a button could be added beside 'Automatic Sort' in the tab order dialog, labelled something like 'Alpha Sort'. I know it would make my life easier. Right now I have to fix tab orders manually; I used a naming scheme to make this easy but it remains a tedious chore for every form I create. Thanks for your consideration of my feature request. -- You are receiving this mail because: You are the assignee for the bug.
core.git: vcl/unx
vcl/unx/gtk4/a11y.cxx | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
New commits:
commit 192bda84402bda175d7620319c019747b24de460
Author: Michael Weghorn
AuthorDate: Thu May 2 09:32:22 2024 +0200
Commit: Michael Weghorn
CommitDate: Fri May 3 07:27:13 2024 +0200
gtk4 a11y: Align role mapping with upstream GTK
Align the gtk4 a11y role mapping with what upstream
GTK 4 does with current git main (as of commit
0064500146fc080dae1ef2b30bebf7bb8b35a52f), see this
upstream GTK commit [0] and the one it refers to for
more details:
commit ad8613876c753cea8695dc8b03dcd37eb8e723a5
Author: Michael Weghorn
Date: Tue Apr 30 14:44:11 2024 +0200
a11y atspi: Improve mapping for container roles
GTK_ACCESSIBLE_ROLE_GENERIC is for
"a nameless container that has no semantic meaning of its own",
for which AT-SPI role ATSPI_ROLE_PANEL [1]
("A generic container that is often used to group
objects.") fits better than ATSPI_ROLE_FILLER
("A object that fills up space in a user interface."),
so map to this one.
With this in place, widgets like GtkBox are again
reported with the panel role on AT-SPI level after
commit a86923de943b6a42ba431be2a336972dca9c587d
("a11y: Change the role for many containers"),
whose commit message suggests that the change
on the AT-SPI level was unintended.
For GTK_ACCESSIBLE_ROLE_GROUP, use the corresponding
ATSPI_ROLE_GROUPING ("A group of related widgets.
This group typically has a label.").
[1] https://docs.gtk.org/atspi2/enum.Role.html
This causes the LO a11y roles `PANEL`, `SPLIT_PANE` and
`ROOT_PANE` to be mapped to the AT-SPI panel role again.
With the above-mentioned GTK upstream change, the native
GTK widgets now also use the panel role without having
to explicitly set anything on LO side rather than being
fillers, which removes the need to set them explicitly,
see the full commit message of
commit f6ca163d3f6383d3a48dbdacc5410e630d678ea1
Author: Michael Weghorn
Date: Fri Apr 26 12:43:24 2024 +0200
gtk4 a11y: Don't create second AT context for OOoFixed
for more details.
Also, map the LO `FILLER` role to `GTK_ACCESSIBLE_ROLE_WIDGET`
which GTK maps to the AT-SPI filler role.
(The previously used `GTK_ACCESSIBLE_ROLE_GENERIC`
is now mapped to the AT-SPI panel role, which
is for widget containers rather than fillers.)
[0]
https://gitlab.gnome.org/GNOME/gtk/-/commit/ad8613876c753cea8695dc8b03dcd37eb8e723a5
Change-Id: I1d1a8f626911455481d2d722790e8915daa921c7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166995
Reviewed-by: Michael Weghorn
Tested-by: Jenkins
diff --git a/vcl/unx/gtk4/a11y.cxx b/vcl/unx/gtk4/a11y.cxx
index bf66b058b231..4860c7cff33d 100644
--- a/vcl/unx/gtk4/a11y.cxx
+++ b/vcl/unx/gtk4/a11y.cxx
@@ -93,10 +93,9 @@ map_accessible_role(const
css::uno::Reference&
eRole = GTK_ACCESSIBLE_ROLE_LINK;
break;
case css::accessibility::AccessibleRole::PANEL:
-eRole = GTK_ACCESSIBLE_ROLE_GROUP;
-break;
case css::accessibility::AccessibleRole::ROOT_PANE:
-eRole = GTK_ACCESSIBLE_ROLE_GROUP;
+case css::accessibility::AccessibleRole::SPLIT_PANE:
+eRole = GTK_ACCESSIBLE_ROLE_GENERIC;
break;
case css::accessibility::AccessibleRole::MENU_BAR:
eRole = GTK_ACCESSIBLE_ROLE_MENU_BAR;
@@ -108,9 +107,6 @@ map_accessible_role(const
css::uno::Reference&
case css::accessibility::AccessibleRole::POPUP_MENU:
eRole = GTK_ACCESSIBLE_ROLE_MENU;
break;
-case css::accessibility::AccessibleRole::SPLIT_PANE:
-eRole = GTK_ACCESSIBLE_ROLE_GROUP;
-break;
case css::accessibility::AccessibleRole::TOOL_BAR:
eRole = GTK_ACCESSIBLE_ROLE_TOOLBAR;
break;
@@ -159,7 +155,8 @@ map_accessible_role(const
css::uno::Reference&
#endif
break;
case css::accessibility::AccessibleRole::FILLER:
-eRole = GTK_ACCESSIBLE_ROLE_GENERIC;
+// GTK maps this to ATSPI_ROLE_FILLER
+eRole = GTK_ACCESSIBLE_ROLE_WIDGET;
break;
case css::accessibility::AccessibleRole::PUSH_BUTTON:
case css::accessibility::AccessibleRole::BUTTON_DROPDOWN:
core.git: Branch 'distro/vector/vector-7.5.9' - 3 commits - drawinglayer/source vcl/win
drawinglayer/source/processor2d/vclprocessor2d.cxx |3 -
vcl/win/gdi/DWriteTextRenderer.cxx | 35 +++--
2 files changed, 26 insertions(+), 12 deletions(-)
New commits:
commit 85c82ad23c64db500e607a3ffb76e3aebfb18102
Author: Mike Kaganski
AuthorDate: Thu May 2 14:23:53 2024 +0500
Commit: Mike Kaganski
CommitDate: Fri May 3 09:39:46 2024 +0500
tdf#160901: partially revert 8557ea84c9336ba8061246f1f46ddb6e02f413a1
It turns out, that the horizontal scale is needed in the applied transform.
Change-Id: Ic07e015f0ddeee3d66653b683d83435d04b9ab81
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167004
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/vcl/win/gdi/DWriteTextRenderer.cxx
b/vcl/win/gdi/DWriteTextRenderer.cxx
index a962cbcbb801..f8c8c93958d7 100644
--- a/vcl/win/gdi/DWriteTextRenderer.cxx
+++ b/vcl/win/gdi/DWriteTextRenderer.cxx
@@ -332,19 +332,32 @@
WinFontTransformGuard::WinFontTransformGuard(ID2D1RenderTarget* pRenderTarget,
bool bIsVertical)
: mpRenderTarget(pRenderTarget)
{
+const float hscale = [ = rLayout.GetFont()]
+{
+const auto& rPattern = font.GetFontSelectPattern();
+if (!rPattern.mnHeight || !rPattern.mnWidth)
+return 1.0;
+return rPattern.mnWidth * font.GetAverageWidthFactor() /
rPattern.mnHeight;
+}();
+
Degree10 angle = rLayout.GetOrientation();
if (bIsVertical)
angle += 900_deg10;
-if (angle)
+if (hscale != 1.0f || angle)
{
D2D1::Matrix3x2F aTransform;
pRenderTarget->GetTransform();
moTransform = aTransform;
+if (hscale != 1.0f) // basegfx::fTools::equal is useless with float
+aTransform = aTransform * D2D1::Matrix3x2F::Scale(hscale, 1.0f, {
0, 0 });
+
// DWrite angle is in clockwise degrees, our orientation is in
counter-clockwise 10th
// degrees.
-aTransform = aTransform *
D2D1::Matrix3x2F::Rotation(-toDegrees(angle), rBaseline);
+if (angle)
+aTransform = aTransform *
D2D1::Matrix3x2F::Rotation(-toDegrees(angle), rBaseline);
+
mpRenderTarget->SetTransform(aTransform);
}
}
commit f1d2339d320dd86c427b93a6e24f4106bf7feb10
Author: Mike Kaganski
AuthorDate: Wed Apr 10 22:45:41 2024 +0500
Commit: Mike Kaganski
CommitDate: Fri May 3 09:39:42 2024 +0500
Only call ID2D1RenderTarget::Get/SetTransform when needed
Change-Id: Ifde2c24c222e3c316f5a4f47e86c2c08f676639a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165983
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/vcl/win/gdi/DWriteTextRenderer.cxx
b/vcl/win/gdi/DWriteTextRenderer.cxx
index fb96cfa68659..a962cbcbb801 100644
--- a/vcl/win/gdi/DWriteTextRenderer.cxx
+++ b/vcl/win/gdi/DWriteTextRenderer.cxx
@@ -108,7 +108,7 @@ public:
private:
ID2D1RenderTarget* mpRenderTarget;
-D2D1::Matrix3x2F maTransform;
+std::optional moTransform;
};
} // end anonymous namespace
@@ -332,25 +332,27 @@
WinFontTransformGuard::WinFontTransformGuard(ID2D1RenderTarget* pRenderTarget,
bool bIsVertical)
: mpRenderTarget(pRenderTarget)
{
-pRenderTarget->GetTransform();
-D2D1::Matrix3x2F aTransform = maTransform;
-
Degree10 angle = rLayout.GetOrientation();
-
if (bIsVertical)
angle += 900_deg10;
if (angle)
{
+D2D1::Matrix3x2F aTransform;
+pRenderTarget->GetTransform();
+moTransform = aTransform;
+
// DWrite angle is in clockwise degrees, our orientation is in
counter-clockwise 10th
// degrees.
-aTransform = aTransform
- * D2D1::Matrix3x2F::Rotation(
- -toDegrees(angle), rBaseline);
+aTransform = aTransform *
D2D1::Matrix3x2F::Rotation(-toDegrees(angle), rBaseline);
+mpRenderTarget->SetTransform(aTransform);
}
-mpRenderTarget->SetTransform(aTransform);
}
-WinFontTransformGuard::~WinFontTransformGuard() {
mpRenderTarget->SetTransform(maTransform); }
+WinFontTransformGuard::~WinFontTransformGuard()
+{
+if (moTransform)
+mpRenderTarget->SetTransform(*moTransform);
+}
/* vim:set shiftwidth=4 softtabstop=4 expandtab: */
commit 331fcd66d047d4b12e4b958f88f92825ddd2acbd
Author: Mike Kaganski
AuthorDate: Fri Apr 26 01:00:21 2024 +0500
Commit: Mike Kaganski
CommitDate: Wed May 1 17:15:32 2024 +0500
tdf#157240: also set font color together with font
Commit b008831a5545e5a777d77547ef96b9798d795f30 (tdf#152990 set the font
after the MapMode is (potentially) set, 2023-01-14) had moved setting of
font forward, but left setting the font color behind. This fixed that.
Change-Id: I73fadc7c139da3b6f84b7fc875c585d02fc1c719
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166654
Tested-by:
[Bug 160697] Writer opens blank window temporarily at launch
https://bugs.documentfoundation.org/show_bug.cgi?id=160697 --- Comment #11 from Michael Weghorn --- (In reply to p.wibberley from comment #8) > Also, I've clearly been confused by the scope of environment variables here, > as > > (a) I can set QT_QPA_PLATFORM in one terminal window and start Writer from > there, and I get the extremely brief soffice.bin window - so it's not my > computer! - but > > (b) if I open a second terminal then QT_QPA_PLATFORM isn't set and I get a > slow soffice.bin window. Yes, an `export QT_QPA_PLATFORM=xcb` only applies for the current terminal, i.e. processes started from there. > Moreover, About Libreoffice shows "VCL:kf5(cairo+xcb)" with QT_QPA_PLATFORM > set but "VCL:kf5(cairo+wayland)" without. I think this is what you suggest > I should see. Yes. > I also see that the terminal window without QT_QPA_PLATFORM > gives error messages, > > "qt.qpa.wayland: Wayland does not support QWindow::requestActivate()" > "This plugin supports grabbing the mouse only for popup windows" This warning is expected and unrelated. > So, presumably, when I'm starting Writer from the launcher menu, it's simply > not seeing QT_QPA_PLATFORM that I set in the first terminal window. Yes, exactly. > Another observation is that if I open Writer from the first terminal window, > and *leave it open* while I start Writer from the second terminal window, > then the second instance of Writer behaves as if QT_QPA_PLATFORM *is* set, > even though running env in the second terminal window shows that it isn't. > May be we should expect that, but I thought it worth noting. Yes, that's expected. LibreOffice doesn't start a new process/"session", but reuses the existing one if it's already running. (In reply to p.wibberley from comment #9) > Oh, and "--nologo" doesn't seem to make any difference. Thanks. So to summarize: There's an "soffice.bin" window showing up temporarily when starting Writer, that then disappears and the actual Writer window shows up. This happens when either running LO as a native Wayland application (starting LO without QT_QPA_PLATFORM=xcb set) and when run with Qt's xcb platform, i.e. on XWayland (starting LO with QT_QPA_PLATFORM=xcb set). For the Wayland case, that "soffice.bin" window is shown much shorter than for the xcb case, but it's still shown. Is that correct? Could you please try whether you see the same when you start LO with environment variable SAL_USE_VCLPLUGIN=gtk3 to force the use of the so-called gtk3 VCL plugin? (Please double-check that "Help" -> "About LibreOffice" shows "VCL: gtk3" then.) -- You are receiving this mail because: You are the assignee for the bug.
core.git: include/vcl vcl/jsdialog vcl/source
include/vcl/jsdialog/executor.hxx |5 +
include/vcl/toolkit/fixed.hxx |2 +-
include/vcl/weld.hxx |2 ++
include/vcl/wintypes.hxx |3 ++-
vcl/jsdialog/executor.cxx | 12
vcl/source/control/fixed.cxx |4 ++--
vcl/source/control/fixedhyper.cxx |2 +-
vcl/source/window/window.cxx |1 +
8 files changed, 26 insertions(+), 5 deletions(-)
New commits:
commit 6f7acc14866136f22d26cae1e8656d8719b58300
Author: Tomaž Vajngerl
AuthorDate: Thu May 2 14:32:52 2024 +0900
Commit: Tomaž Vajngerl
CommitDate: Fri May 3 07:13:22 2024 +0200
jsdialog: support for LinkButton as an independent widget
This adds support for the (weld)LinkButton (FixedHyperlink) as an
independent widget and not part of FixedText to jsdialog. In addition
add "click" event that triggers activate_link method.
Change-Id: Id110b4a0fd60fc24592e00235243783d46ae4575
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166898
Tested-by: Jenkins
Reviewed-by: Tomaž Vajngerl
diff --git a/include/vcl/jsdialog/executor.hxx
b/include/vcl/jsdialog/executor.hxx
index b60c035d587a..ef667a70ce26 100644
--- a/include/vcl/jsdialog/executor.hxx
+++ b/include/vcl/jsdialog/executor.hxx
@@ -126,6 +126,11 @@ public:
{
rNotebook.m_aLeavePageHdl.Call(rPage);
}
+
+static bool activate_link(weld::LinkButton& rLinkButton)
+{
+return rLinkButton.signal_activate_link();
+}
};
namespace jsdialog
diff --git a/include/vcl/toolkit/fixed.hxx b/include/vcl/toolkit/fixed.hxx
index f4c410c974af..313e717c5a2f 100644
--- a/include/vcl/toolkit/fixed.hxx
+++ b/include/vcl/toolkit/fixed.hxx
@@ -53,7 +53,7 @@ protected:
virtual vcl::Window* getAccessibleRelationLabelFor() const override;
public:
-explicitFixedText( vcl::Window* pParent, WinBits nStyle = 0 );
+explicit FixedText(vcl::Window* pParent, WinBits nStyle = 0, WindowType
eType = WindowType::FIXEDTEXT);
virtual ~FixedText() override;
virtual voiddispose() override;
diff --git a/include/vcl/weld.hxx b/include/vcl/weld.hxx
index 8b9495e9e4e8..bd394dc5d3bc 100644
--- a/include/vcl/weld.hxx
+++ b/include/vcl/weld.hxx
@@ -1665,6 +1665,8 @@ class VCL_DLLPUBLIC RadioButton : virtual public
CheckButton
class VCL_DLLPUBLIC LinkButton : virtual public Widget
{
+friend class ::LOKTrigger;
+
Link m_aActivateLinkHdl;
protected:
diff --git a/include/vcl/wintypes.hxx b/include/vcl/wintypes.hxx
index c025e83b0afe..d0d6208d735b 100644
--- a/include/vcl/wintypes.hxx
+++ b/include/vcl/wintypes.hxx
@@ -99,7 +99,8 @@ enum class WindowType : sal_uInt16
HEADERBAR,
VERTICALTABCONTROL ,
PROGRESSBAR ,
-LAST = PROGRESSBAR,
+LINK_BUTTON,
+LAST = LINK_BUTTON,
// only used in vclxtoolkit.cxx
TOOLKIT_FRAMEWINDOW= 0x1000,
TOOLKIT_SYSTEMCHILDWINDOW = 0x1001,
diff --git a/vcl/jsdialog/executor.cxx b/vcl/jsdialog/executor.cxx
index 7c36eb3bdc1e..3eebd350ef88 100644
--- a/vcl/jsdialog/executor.cxx
+++ b/vcl/jsdialog/executor.cxx
@@ -164,6 +164,18 @@ bool ExecuteAction(const OUString& nWindowId, const
OUString& rWidget, StringMap
}
}
}
+else if (sControlType == "linkbutton")
+{
+auto pButton = dynamic_cast(pWidget);
+if (pButton)
+{
+if (sAction == "click")
+{
+LOKTrigger::activate_link(*pButton);
+return true;
+}
+}
+}
else if (sControlType == "menubutton")
{
auto pButton = dynamic_cast(pWidget);
diff --git a/vcl/source/control/fixed.cxx b/vcl/source/control/fixed.cxx
index 068332e5b610..ce5bbf486c85 100644
--- a/vcl/source/control/fixed.cxx
+++ b/vcl/source/control/fixed.cxx
@@ -94,8 +94,8 @@ const Color& FixedText::GetCanonicalTextColor( const
StyleSettings& _rStyle ) co
return _rStyle.GetLabelTextColor();
}
-FixedText::FixedText( vcl::Window* pParent, WinBits nStyle )
-: Control(WindowType::FIXEDTEXT)
+FixedText::FixedText(vcl::Window* pParent, WinBits nStyle, WindowType eType)
+: Control(eType)
, m_nMaxWidthChars(-1)
, m_nMinWidthChars(-1)
, m_pMnemonicWindow(nullptr)
diff --git a/vcl/source/control/fixedhyper.cxx
b/vcl/source/control/fixedhyper.cxx
index 5b4960d92f86..5c8e9e4a29d1 100644
--- a/vcl/source/control/fixedhyper.cxx
+++ b/vcl/source/control/fixedhyper.cxx
@@ -34,7 +34,7 @@
using namespace css;
FixedHyperlink::FixedHyperlink(vcl::Window* pParent, WinBits nWinStyle)
-: FixedText(pParent, nWinStyle)
+: FixedText(pParent, nWinStyle, WindowType::LINK_BUTTON)
, m_nTextLen(0)
, m_aOldPointer(PointerStyle::Arrow)
{
diff --git a/vcl/source/window/window.cxx b/vcl/source/window/window.cxx
index 3dd289ddb1b3..06a60a209483 100644
---
[Bug 105066] Paste special by select bitmap on same cell will become to one blank image frame on sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=105066 Stéphane Guillou (stragu) changed: What|Removed |Added Version|4.4.6.3 release |4.4.2.2 release Keywords||bibisectRequest, regression --- Comment #15 from Stéphane Guillou (stragu) --- Bibisected with linux-64-releases to first affected release libreoffice-4.4.2.1. Also reproduced at that version with bug 107529 steps. Need a closer bibisect, Henry's fixes might be related: https://wiki.documentfoundation.org/Releases/4.4.2/RC1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105066] Paste special by select bitmap on same cell will become to one blank image frame on sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=105066 --- Comment #14 from Stéphane Guillou (stragu) --- (In reply to Stéphane Guillou (stragu) from comment #13) > I can't confirm that on Linux, I always > get to 5.0 being the earliest. Actually, I can, using the "Bitmap" option in Paste Special, with the linux-64-releases bibisect repo checked out at libreoffice-4.4.6.3 and the gen VCL plugin: Version: 4.4.6.3 Build ID: e8938fd3328e95dcf59dd64e7facd2c7d67c704d Locale: en_AU.UTF-8 Will have a closer look at why there's a difference. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105066] Paste special by select bitmap on same cell will become to one blank image frame on sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=105066 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org, tele...@surfxs.nl --- Comment #13 from Stéphane Guillou (stragu) --- Tempted to close this as duplicate of (younger) bug 107529 (because it has been bibisected). However, Telesto reports reproducing in an earlier version in comment 3: 4.4.6.3 on Windows. I can't confirm that on Linux, I always get to 5.0 being the earliest. Are you still able to double-check 4.4 vs 5.0 with comment 0 steps, Telesto? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107529] Image disappears when inserting 2 images at the same location
https://bugs.documentfoundation.org/show_bug.cgi?id=107529 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |4042| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134042] [EDITING] When paste image on another image, they break and vanish. Calc eventually crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=134042 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=10 | |5066, | |https://bugs.documentfounda | |tion.org/show_bug.cgi?id=10 | |7529| CC||stephane.guillou@libreoffic ||e.org -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105066] Paste special by select bitmap on same cell will become to one blank image frame on sheet.
https://bugs.documentfoundation.org/show_bug.cgi?id=105066 Stéphane Guillou (stragu) changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |4042| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Bug 133092 depends on bug 134042, which changed state. Bug 134042 Summary: [EDITING] When paste image on another image, they break and vanish. Calc eventually crashes https://bugs.documentfoundation.org/show_bug.cgi?id=134042 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107529] Image disappears when inserting 2 images at the same location
https://bugs.documentfoundation.org/show_bug.cgi?id=107529 Stéphane Guillou (stragu) changed: What|Removed |Added CC||pox_...@yahoo.com --- Comment #10 from Stéphane Guillou (stragu) --- *** Bug 134042 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134042] [EDITING] When paste image on another image, they break and vanish. Calc eventually crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=134042 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Version|6.4.1.2 release |6.4.0.3 release Status|REOPENED|RESOLVED OS|Windows (All) |All --- Comment #7 from Stéphane Guillou (stragu) --- With image copied from Firefox, reproduced as described in comment 0 with: Version: 6.4.0.3 Build ID: b0a288ab3d2d4774cb44b62f04d5d28733ac6df8 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: CL ...as well as 7.3.0.3 and a recent trunk build: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ce454f382d0d005dd3de021c7820be3ffa0bb582 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded No crash though. This is in essence the same issue as described in bug 107529 and bug 126920, regardless of how slightly different the steps were. Consolidating will help attract developer attention to the issue. (Still unsure about bug 105066 because of the earlier version reported.) *** This bug has been marked as a duplicate of bug 107529 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145127] LibreOfficeKit macOS?
https://bugs.documentfoundation.org/show_bug.cgi?id=145127 Olly Betts changed: What|Removed |Added CC||ojwbetts...@gmail.com --- Comment #3 from Olly Betts --- For the record (since the linked logs will expire eventually) the homebrew libreoffice package version used in my test was: LibreOffice_24.2.3_MacOS_aarch64.dmg -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116280] [META] Regressions introduced by the image handling refactoring
https://bugs.documentfoundation.org/show_bug.cgi?id=116280 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|126920 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126920 [Bug 126920] LibreOffice Calc is oversensitive to pasting overlapping images -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105584] [META] Calc image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105584 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|126920 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=126920 [Bug 126920] LibreOffice Calc is oversensitive to pasting overlapping images -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107529] Image disappears when inserting 2 images at the same location
https://bugs.documentfoundation.org/show_bug.cgi?id=107529 Stéphane Guillou (stragu) changed: What|Removed |Added CC||chrisshaw...@gmail.com --- Comment #9 from Stéphane Guillou (stragu) --- *** Bug 126920 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 126920] LibreOffice Calc is oversensitive to pasting overlapping images
https://bugs.documentfoundation.org/show_bug.cgi?id=126920
Stéphane Guillou (stragu) changed:
What|Removed |Added
Status|NEW |RESOLVED
Blocks|105584, 116280 |
Resolution|--- |DUPLICATE
CC||stephane.guillou@libreoffic
||e.org
--- Comment #12 from Stéphane Guillou (stragu)
---
(In reply to Timur from comment #9)
> In 6.1 repo there was 2nd change, paste to B2 started behaving as reported
> ("Image 1..." in B1). Here is the commit (only found in bug 117576).
>
> commit 8481c07a624f6b49ff535cb2d4adbc8243b279a3
> authorTomaž Vajngerl 2018-04-01
> 14:47:13
> +0900
> commit e4eb416c3ef81d098ed61caabd2077cbbb2418bc (patch)
> remove swapping and link from GraphicObject and Graphic
I see the issue starting at 5.0. After a second paste, one needs to zoom in/out
to refresh the view and see the empty frame.
I checked with the commit you bibisected to: empty frame directly at second
paste at e4eb416c, but same thing after a zoom in/out refresh at e4eb416c~1, so
Quikee only made something pre-existing more visible.
Marking as duplicate of bug 107529.
*** This bug has been marked as a duplicate of bug 107529 ***
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=105584
[Bug 105584] [META] Calc image bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=116280
[Bug 116280] [META] Regressions introduced by the image handling refactoring
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 135538] Search-Replace: Regular Expression engine fails on zero length matches
https://bugs.documentfoundation.org/show_bug.cgi?id=135538 Mike Kaganski changed: What|Removed |Added CC||chris@penalvch.online --- Comment #16 from Mike Kaganski --- *** Bug 160118 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160118] Find and replace doesn't find regular expression ^
https://bugs.documentfoundation.org/show_bug.cgi?id=160118 --- Comment #7 from Mike Kaganski --- *** This bug has been marked as a duplicate of bug 135538 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146076] [META] Find & Replace Regular Expressions
https://bugs.documentfoundation.org/show_bug.cgi?id=146076 Bug 146076 depends on bug 145774, which changed state. Bug 145774 Summary: Find and Replace (with regular expression option): ^ is not found in search https://bugs.documentfoundation.org/show_bug.cgi?id=145774 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Bug 135538] Search-Replace: Regular Expression engine fails on zero length matches
https://bugs.documentfoundation.org/show_bug.cgi?id=135538 Mike Kaganski changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=14 | |5774| --- Comment #15 from Mike Kaganski --- *** Bug 145774 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145774] Find and Replace (with regular expression option): ^ is not found in search
https://bugs.documentfoundation.org/show_bug.cgi?id=145774 Mike Kaganski changed: What|Removed |Added See Also|https://bugs.documentfounda | |tion.org/show_bug.cgi?id=13 | |5538| Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #7 from Mike Kaganski --- This is exactly tdf#135538. The special processing of $ is unrelated, and just distorts the perspective. This whole problem is about inability to find zero-length match, with both elaborate pre/postconditions, or special cases of pre/postconditions like ^ or \b are all nor handled by their own. *** This bug has been marked as a duplicate of bug 135538 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160917] Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160917 Stéphane Guillou (stragu) changed: What|Removed |Added Regression By||Jim Raykowski -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104160] [META] Bugs and features related to multiple monitor setups
https://bugs.documentfoundation.org/show_bug.cgi?id=104160 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on|160917 | Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160917 [Bug 160917] Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103182] [META] GTK3-specific bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=103182 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160917 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160917 [Bug 160917] Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160917] Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160917 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks|104160 |103182 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103182 [Bug 103182] [META] GTK3-specific bugs https://bugs.documentfoundation.org/show_bug.cgi?id=104160 [Bug 104160] [META] Bugs and features related to multiple monitor setups -- You are receiving this mail because: You are the assignee for the bug.
[Bug 133092] [META] Crash bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=133092 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160917 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160917 [Bug 160917] Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 118526] CRASH: Notebookbar crashes in read mode
https://bugs.documentfoundation.org/show_bug.cgi?id=118526 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0917 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160917 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160917 [Bug 160917] Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160917] New: Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=160917 Bug ID: 160917 Summary: Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer Product: LibreOffice Version: 6.4.0.3 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Keywords: bibisected, bisected, regression Severity: critical Priority: low Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org CC: rayk...@gmail.com Blocks: 104160, 107237, 133092 Created attachment 193945 --> https://bugs.documentfoundation.org/attachment.cgi?id=193945=edit crash minidump Steps: 0. Use the tabbed UI with View > User Interface 1. Close LO completely 2. Open Writer 3. Very quickly click the right-hand-side hamburger/cog menu 4. Wait for the menu to open and the UI to finish loading 5. Click elsewhere to close the menu, e.g. on document canvas Result: crash I could only reproduce with the gtk3 VCL plugin. I couldn't reproduce in Draw or Calc. Repro on Ubuntu 22.04 + GNOME 42.9 and: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ce454f382d0d005dd3de021c7820be3ffa0bb582 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded - 24.2.2.2: https://crashreport.libreoffice.org/stats/crash_details/26fe3353-8f84-4907-99cc-6af5f8b9d29e - 7.6.6.3 with signature "vcl::Window::GetWindowExtentsRelative(vcl::Window const*) const": https://crashreport.libreoffice.org/stats/crash_details/922a5571-00b2-4861-a68a-45dcfa454d04 - 7.3.0.3, as above: https://crashreport.libreoffice.org/stats/crash_details/60b9604c-0945-4b37-979a-f6859bd6298b - 7.2.0.4 with signature "vcl::Window::ImplGetWindowExtentsRelative(vcl::Window const*) const": https://crashreport.libreoffice.org/stats/crash_details/9cbe59ad-02f3-4e3b-bf21-a0206c44f587 - 7.1.0.3 with signature "vcl::Window::ImplGetWindowExtentsRelative": https://crashreport.libreoffice.org/stats/crash_details/51ac6e2a-8d9b-4c5c-a2fe-c771c8b4c959 - 6.4.0.3, as above: https://crashreport.libreoffice.org/stats/crash_details/188c1ad4-9397-46de-aefd-39d9b1c6003e Bibisected with linux-64-6.4 to first bad build [059faab4dd14e46b04bda51715362300da7f60ee] which points to: commit 4ae5fe896e96d082e21788ae6d42a67133567ba7 author Jim Raykowski Sat Nov 09 16:07:09 2019 -0900 committer Xisco Faulí Mon Nov 11 11:04:56 2019 +0100 tdf#118526 Reload Notebookbar if read mode has switched Reviewed-on: https://gerrit.libreoffice.org/82371 Jim, can you please have a look? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104160 [Bug 104160] [META] Bugs and features related to multiple monitor setups https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed https://bugs.documentfoundation.org/show_bug.cgi?id=133092 [Bug 133092] [META] Crash bugs -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104160] [META] Bugs and features related to multiple monitor setups
https://bugs.documentfoundation.org/show_bug.cgi?id=104160 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||160917 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160917 [Bug 160917] Crash when opening and closing Tabbed UI's hamburger/cog menu while UI loading in Writer -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157353] Drag-and-dropping data source column headings onto spreadsheet does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=157353 --- Comment #6 from QA Administrators --- Dear João Pedro Torres, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160697] Writer opens blank window temporarily at launch
https://bugs.documentfoundation.org/show_bug.cgi?id=160697 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160701] OpenPGP warning when encrypting with an untrusted public key: rename from "Error" to "Warning"
https://bugs.documentfoundation.org/show_bug.cgi?id=160701 QA Administrators changed: What|Removed |Added Whiteboard| QA:needsComment| -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160697] Writer opens blank window temporarily at launch
https://bugs.documentfoundation.org/show_bug.cgi?id=160697 --- Comment #10 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160722] UI: Menu bar doesn't repaint to show disabled items
https://bugs.documentfoundation.org/show_bug.cgi?id=160722 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 150421] FILESAVE DOC: Liberation Serif added across the document as DF on DOC export in a hebrew document
https://bugs.documentfoundation.org/show_bug.cgi?id=150421 --- Comment #4 from QA Administrators --- Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154850] From Impress if I export an image to svg format, the result is wrong
https://bugs.documentfoundation.org/show_bug.cgi?id=154850 --- Comment #6 from QA Administrators --- Dear Gustavo Panter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157352] Feature request: Format individual user's comments
https://bugs.documentfoundation.org/show_bug.cgi?id=157352 --- Comment #4 from QA Administrators --- Dear Jack Wallen, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147455] Openeuler base compiled libreoffice-base 6.4.7 crashes when creating database table file
https://bugs.documentfoundation.org/show_bug.cgi?id=147455 --- Comment #7 from QA Administrators --- Dear zhangke, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 147454] openeuler build libreoffice-impress ppt crash
https://bugs.documentfoundation.org/show_bug.cgi?id=147454 --- Comment #8 from QA Administrators --- Dear zhangke, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87351] [META] Conditional formatting bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87351 Bug 87351 depends on bug 146663, which changed state. Bug 146663 Summary: Applying paragraph styles resets Character direct formatting https://bugs.documentfoundation.org/show_bug.cgi?id=146663 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146663] Applying paragraph styles resets Character direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146663 --- Comment #10 from QA Administrators --- Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146663] Applying paragraph styles resets Character direct formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=146663 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=87740 Bug 87740 depends on bug 134079, which changed state. Bug 134079 Summary: Layout freeze with specific document and an image anchored to character at the wrong spot https://bugs.documentfoundation.org/show_bug.cgi?id=134079 What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134079] Layout freeze with specific document and an image anchored to character at the wrong spot
https://bugs.documentfoundation.org/show_bug.cgi?id=134079 --- Comment #17 from QA Administrators --- Dear Telesto, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Bug 134079] Layout freeze with specific document and an image anchored to character at the wrong spot
https://bugs.documentfoundation.org/show_bug.cgi?id=134079 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Bug 95283] Undo does not work with inserted formula object in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=95283 --- Comment #7 from QA Administrators --- Dear Gan, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 89468] Automatic hyperlink creation to file system does not work as expected when editing existing text
https://bugs.documentfoundation.org/show_bug.cgi?id=89468 --- Comment #14 from QA Administrators --- Dear pb, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 34585] Frame with no-fill background has white background instead of transparent
https://bugs.documentfoundation.org/show_bug.cgi?id=34585 --- Comment #29 from QA Administrators --- Dear Kissaki, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148599] Frame style issues with direct formatting of frame area
https://bugs.documentfoundation.org/show_bug.cgi?id=148599 --- Comment #5 from QA Administrators --- Dear lahos, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 148274] AutoText from LO > 7.3 (or maybe > 7.0..?) incompatible with older versions
https://bugs.documentfoundation.org/show_bug.cgi?id=148274 --- Comment #5 from QA Administrators --- Dear Cor Nouws, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 145313] EDITING ODT Moving the penultimate list item will insert a new empty numbered list item
https://bugs.documentfoundation.org/show_bug.cgi?id=145313 --- Comment #4 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144961] Font matching issues
https://bugs.documentfoundation.org/show_bug.cgi?id=144961 --- Comment #19 from QA Administrators --- Dear Chris Sherlock, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 143295] DateAcceptancePattern is wrong in Korean.
https://bugs.documentfoundation.org/show_bug.cgi?id=143295 --- Comment #6 from QA Administrators --- Dear DaeHyun Sung, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142918] FILEOPEN PPTX Slideshow setting “Without animations” not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=142918 --- Comment #3 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141393] FILEOPEN PPTX Shapes on different slides with same name navigate to the first occurrence
https://bugs.documentfoundation.org/show_bug.cgi?id=141393 --- Comment #7 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141261] EDITING Insertions in margin mode shows $2 in margin for comments
https://bugs.documentfoundation.org/show_bug.cgi?id=141261 --- Comment #5 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 141013] Several 'More Fields' dialogs are opened in a MailMerge document with password-protected DB when the dialog is kept open when closing previous document
https://bugs.documentfoundation.org/show_bug.cgi?id=141013 --- Comment #9 from QA Administrators --- Dear Mike Kaganski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132416] IMAGE FRAME: Table isn't split with anchor to character left cell; table splits after moving it to right cell
https://bugs.documentfoundation.org/show_bug.cgi?id=132416 --- Comment #6 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132413] Page layout changes after save & reload (related to image anchored to character)
https://bugs.documentfoundation.org/show_bug.cgi?id=132413 --- Comment #12 from QA Administrators --- Dear Telesto, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139531] EDITING Turning on/off display of tracked changes moves view
https://bugs.documentfoundation.org/show_bug.cgi?id=139531 --- Comment #9 from QA Administrators --- Dear NISZ LibreOffice Team, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 130154] i18n: update locale data for Estonian [et-EE]
https://bugs.documentfoundation.org/show_bug.cgi?id=130154 --- Comment #12 from QA Administrators --- Dear Mihkel Tõnnov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 131671] Change of data point icon color in Calc's XY Chart not reflected in preview
https://bugs.documentfoundation.org/show_bug.cgi?id=131671 --- Comment #4 from QA Administrators --- Dear alanandpenny, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 117692] Frame at top of page moves into header with wrong padding when reloading exported DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=117692 --- Comment #29 from QA Administrators --- Dear Aron Budea, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 123226] Pivot table if Filter is used and then turned off, then column filter stops working
https://bugs.documentfoundation.org/show_bug.cgi?id=123226 --- Comment #7 from QA Administrators --- Dear grofaty, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120288] FILESAVE XLSX Default font style affects the height of rows in Excel
https://bugs.documentfoundation.org/show_bug.cgi?id=120288 --- Comment #13 from QA Administrators --- Dear Gabor Kelemen (allotropia), To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116623] [EMF] FILEOPEN The curves extend outside the plot area
https://bugs.documentfoundation.org/show_bug.cgi?id=116623 --- Comment #6 from QA Administrators --- Dear johan, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107735] FILESAVE, ODF: element in needs to reference a style of family type table
https://bugs.documentfoundation.org/show_bug.cgi?id=107735 --- Comment #7 from QA Administrators --- Dear Regina Henschel, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 100145] FILEOPEN: PPTX: Hide after animation doesn't work as expected
https://bugs.documentfoundation.org/show_bug.cgi?id=100145 --- Comment #10 from QA Administrators --- Dear Ofir, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160915] Please add option to not save OLE replacement objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160915 Mike Kaganski changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | Ever confirmed|0 |1 --- Comment #2 from Mike Kaganski --- https://gerrit.libreoffice.org/c/core/+/167026 -- You are receiving this mail because: You are the assignee for the bug.
core.git: vcl/win
vcl/win/gdi/DWriteTextRenderer.cxx | 17 +++--
1 file changed, 15 insertions(+), 2 deletions(-)
New commits:
commit 3f2d56d486da2006e2cfa6f2f63700a14fae
Author: Mike Kaganski
AuthorDate: Thu May 2 14:23:53 2024 +0500
Commit: Mike Kaganski
CommitDate: Fri May 3 03:51:45 2024 +0200
tdf#160901: partially revert 8557ea84c9336ba8061246f1f46ddb6e02f413a1
It turns out, that the horizontal scale is needed in the applied transform.
Change-Id: Ic07e015f0ddeee3d66653b683d83435d04b9ab81
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/167004
Tested-by: Jenkins
Reviewed-by: Mike Kaganski
diff --git a/vcl/win/gdi/DWriteTextRenderer.cxx
b/vcl/win/gdi/DWriteTextRenderer.cxx
index 37c8f2aa217b..8a62f2d73fd9 100644
--- a/vcl/win/gdi/DWriteTextRenderer.cxx
+++ b/vcl/win/gdi/DWriteTextRenderer.cxx
@@ -311,19 +311,32 @@
WinFontTransformGuard::WinFontTransformGuard(ID2D1RenderTarget* pRenderTarget,
bool bIsVertical)
: mpRenderTarget(pRenderTarget)
{
+const float hscale = [ = rLayout.GetFont()]
+{
+const auto& rPattern = font.GetFontSelectPattern();
+if (!rPattern.mnHeight || !rPattern.mnWidth)
+return 1.0;
+return rPattern.mnWidth * font.GetAverageWidthFactor() /
rPattern.mnHeight;
+}();
+
Degree10 angle = rLayout.GetOrientation();
if (bIsVertical)
angle += 900_deg10;
-if (angle)
+if (hscale != 1.0f || angle)
{
D2D1::Matrix3x2F aTransform;
pRenderTarget->GetTransform();
moTransform = aTransform;
+if (hscale != 1.0f) // basegfx::fTools::equal is useless with float
+aTransform = aTransform * D2D1::Matrix3x2F::Scale(hscale, 1.0f, {
0, 0 });
+
// DWrite angle is in clockwise degrees, our orientation is in
counter-clockwise 10th
// degrees.
-aTransform = aTransform *
D2D1::Matrix3x2F::Rotation(-toDegrees(angle), rBaseline);
+if (angle)
+aTransform = aTransform *
D2D1::Matrix3x2F::Rotation(-toDegrees(angle), rBaseline);
+
mpRenderTarget->SetTransform(aTransform);
}
}
[Bug 145127] LibreOfficeKit macOS?
https://bugs.documentfoundation.org/show_bug.cgi?id=145127 Olly Betts changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 --- Comment #2 from Olly Betts --- I don't have a mac, but I've tested in github actions and libreofficekit still seems broken on macos. Things have improved marginally as it now throws an exception instead of hanging: Calling lok_cpp_init() *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'NSWindow should only be instantiated on the main thread!' *** First throw call stack: ( 0 CoreFoundation 0x00019ddbaccc __exceptionPreprocess + 176 1 libobjc.A.dylib 0x00019d8a2788 objc_exception_throw + 60 2 CoreFoundation 0x00019dddfc48 _CFBundleGetValueForInfoKey + 0 3 AppKit 0x0001a15ad294 -[NSWindow _initContent:styleMask:backing:defer:contentView:] + 188 4 AppKit 0x0001a15ad1cc -[NSWindow initWithContentRect:styleMask:backing:defer:] + 48 5 AppKit 0x0001a185d1e0 -[NSComboBoxWindow initWithContentRect:comboBoxCell:] + 88 6 AppKit 0x0001a185cbd8 -[NSComboBoxCell initPopUpWindow] + 896 7 AppKit 0x0001a18ae404 -[NSComboBoxCell initTextCell:] + 100 8 libvclplug_osxlo.dylib 0x000106eb9f60 _ZN15AquaSalInstanceC2Ev + 448 9 libvclplug_osxlo.dylib 0x000106eb9d30 create_SalInstance + 248 10 libvcllo.dylib 0x000105287e20 _ZN12_GLOBAL__N_111tryInstanceERKN3rtl8OUStringEb + 212 11 libvcllo.dylib 0x000105287be8 _Z17CreateSalInstancev + 272 12 libvcllo.dylib 0x0001052d6668 _Z7InitVCLv + 140 13 libvcllo.dylib 0x0001052d6380 _Z10ImplSVMainv + 328 14 libsofficeapp.dylib 0x00010070c4d8 soffice_main + 216 15 libsofficeapp.dylib 0x000100752e38 _ZL12lo_startmainPv + 52 16 libuno_sal.dylib.3 0x0001008ec69c _ZL21osl_thread_start_ImplPv + 128 17 libsystem_pthread.dylib 0x00019dc66f94 _pthread_start + 136 18 libsystem_pthread.dylib 0x00019dc61d34 thread_start + 8 ) libc++abi: terminating due to uncaught exception of type NSException /Users/runner/work/_temp/a1d11d20-8921-4beb-89f9-c687f1d039b8.sh: line 2: 5369 Abort trap: 6 LO_PATH=/Applications/LibreOffice.app/Contents/Frameworks ./loktest in.html out.doc The repo with the test code is: https://github.com/ojwb/loktest (I've stuck a copy of the LOK headers in the repo as the homebrew LO package doesn't seem to include them.) Logs from the action (though they'll expire after a while): https://github.com/ojwb/loktest/actions/runs/8932805167 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160915] Please add option to not save OLE replacement objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160915 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Then should be forced to always redraw the chart at opening the file? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160913] Freeze pasting complex table inside complex table in multipage view
https://bugs.documentfoundation.org/show_bug.cgi?id=160913 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Looks the same issue as in tdf#160303 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160911] The text in a form is displayed incorrectly
https://bugs.documentfoundation.org/show_bug.cgi?id=160911 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #1 from m_a_riosv --- Reproducible with çVersion: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: f4ef5435df5560e6b6b061ce4053c71e2819bf51 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded By making the text box a little wider, it is then displayed correctly. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160910] Clicking at the end of a line sends at the start of the next one, when there's a line break.
https://bugs.documentfoundation.org/show_bug.cgi?id=160910 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- I can't reproduce. Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Please attach a sample file, reduce the size as much as possible without private information, and paste the information in Menu/Help/About LibreOffice, there is a copy icon. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104160] [META] Bugs and features related to multiple monitor setups
https://bugs.documentfoundation.org/show_bug.cgi?id=104160 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154592 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154592 [Bug 154592] When using multiple monitors, the hamburger menu popup opens on a different screen (Linux) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154592] When using multiple monitors, the hamburger menu popup opens on a different screen (Linux)
https://bugs.documentfoundation.org/show_bug.cgi?id=154592 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||104160 Summary|When using multiple |When using multiple |monitors, the hamburger |monitors, the hamburger |menu popup opens on a |menu popup opens on a |different screen|different screen (Linux) --- Comment #6 from Stéphane Guillou (stragu) --- Still reproduced with: Version: 24.2.2.2 (X86_64) and Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: ce454f382d0d005dd3de021c7820be3ffa0bb582 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Maybe should be compared to other menus on the right edge that behave as expected: - Start Center hamburger - Sidebar hamburger - Tabbed menus under the hamburger/cog (like "Home") Windows equivalent is bug 132139, keeping separate as I'm unsure if the different VCL plugins + OS's different multimonitor handling mean different fixes. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104160 [Bug 104160] [META] Bugs and features related to multiple monitor setups -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160916] New: Tip of the Day typo 9/225 "checbox"
https://bugs.documentfoundation.org/show_bug.cgi?id=160916 Bug ID: 160916 Summary: Tip of the Day typo 9/225 "checbox" Product: LibreOffice Version: 24.2.1.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: trivial Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sk.ione...@gmail.com Created attachment 193944 --> https://bugs.documentfoundation.org/attachment.cgi?id=193944=edit Checbox [sic] typo for tip 9/225 Tip of the Day 9/225 When displaying the fillable form elements, lists the checkbox item as "Checbox." The items within the "Form Controls" section of the Insert>Form Control groups do have the alternate formatting "Check Box." P.S. Typo may be present within other options of the software suite (e.g., Writer) but only confirmed for the Tip of the Day for Calc. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 146977] Tooltips for Sidebar extend off visible display, multi-head with different display resolutions
https://bugs.documentfoundation.org/show_bug.cgi?id=146977 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||2139 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154592] When using multiple monitors, the hamburger menu popup opens on a different screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154592 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||2139 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 132139] Tabbed User Interface Hamburger menu outside of screen when window is maximized (Windows)
https://bugs.documentfoundation.org/show_bug.cgi?id=132139 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Tabbed User Interface |Tabbed User Interface |Hamburger menu outside of |Hamburger menu outside of |screen when window is |screen when window is |maximized |maximized (Windows) OS|All |Windows (All) CC||stephane.guillou@libreoffic ||e.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6977, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4592 Version|Inherited From OOo |6.4.2.2 release Blocks||107237 --- Comment #12 from Stéphane Guillou (stragu) --- (In reply to Sebastiaan Veld from comment #2) > * hoovering over the sidebar icons the pop up information shows up on the > lowerright of the sidebar main selection items (Properties of the Sidebar, > Properties, Page,...) so most of the text banner falls outside of the screen. Let's stick to one issue per report. The tooltip issue is already tracked in bug 146977. Marking some comments as "off topic", and changing version back to the original one. (Tabbed UI was made non-experimental in LO 6.2.) Let's keep this report as Windows-specific, there's also a report for Linux: bug 154592. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||132139 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132139 [Bug 132139] Tabbed User Interface Hamburger menu outside of screen when window is maximized (Windows) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160914] Hamburger menu opens on second monitor
https://bugs.documentfoundation.org/show_bug.cgi?id=160914 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||stephane.guillou@libreoffic ||e.org --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report! This is already tracked in bug 154592, so marking as duplicate. *** This bug has been marked as a duplicate of bug 154592 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 154592] When using multiple monitors, the hamburger menu popup opens on a different screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154592 Stéphane Guillou (stragu) changed: What|Removed |Added CC||patcollins2...@gmail.com --- Comment #5 from Stéphane Guillou (stragu) --- *** Bug 160914 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
Problems with ODF and LibreOffice for 3D-scenes and 3D-objects.
Hi all, this is about ODF 19.99 dr3d:lighting-mode, 20.86 dr3d:lighting-mode, 20.87 dr3d:normals-direction and 20.76 dr3d:backface-culling, and LibreOffice D3DSceneTwoSidedLighting, D3DDoubleSided and D3DNormalsInvert. If you know them, you can skip the explanation and go down to "Problems". ODF has the scene attribute 19.99 dr3d:lighting-mode (values true/false) with meaning, "The dr3d:lighting-mode attribute specifies whether lighting is used in a three-dimensional scene." ODF has the graphic property 20.86 dr3d:lighting-mode (values double-sided/standard) for 3D-objects with meaning, "double-sided: the front and back sides of all planes are displayed if they are visible from the viewer's perspective." "standard: Depending on the value of the dr3d:normals-direction 20.87 attribute, only the front or only the back side sides of the plane are displayed. The opposite sides are not displayed, whether they are visible from the viewer's perspective or not." ODF has the graphic property 20.87 dr3d:normals-direction (values inverse/normal) for 3D-objects with meaning, "inverse: only the back sides of planes are displayed." "normal: only the front sides of planes are displayed." "This graphic property is ignored in case the dr3d:lighting-mode (20.86) has the value "double-sided". The graphic property dr3d:normals-direction is mapped to the property D3DNormalsInvert. That is icon "Invert Normals" in the UI. ODF has the graphic property 20.76 dr3d:backface-culling (values disabled/enabled) for 3D-objects with meaning, "The dr3d:backface-culling attribute specifies whether backface culling is enabled." This graphic property is mapped to the LO property D3DDoubleSided. That belongs to the icon "Double-Sided" in the UI. Problems (1) LibreOffice maps the 19.99 dr3d:lighting-mode scene attribute to the property D3DSceneTwoSidedLighting. That is icon "Double-Sided Illumination" in the UI. Actually this determines whether both front and back face are affected by the directional lights or only one of them. According ODF 19.99 dr3d:lighting-mode should turn lighting in general on or off. (2) LibreOffice ignores the graphic property 20.86 dr3d:lighting-mode on import. It is lost when you open and save a document. (3) The relationship between ODF graphic properties 20.76 dr3d:backface-culling and 20.86 dr3d:lighting-mode is unclear. (4) Turning "Double-Sided" off (=backface-culling on) and inverting the normals, does not make a back face visible. So backface-culling on/off is not a replacement for the missing 20.86 dr3d:lighting-mode. (5) The current way D3DSceneTwoSidedLighting and D3DNormalsInvert work together has no corresponding attribute or graphic property in ODF. For testing you can use the "Shell" object from the predefined 3D-shapes. A cube with an image fill with some transparency is a good test candidate too. Should ODF and LibreOffice be aligned? If yes, in what steps can this be done? Kind regards, Regina
[Bug 160915] New: Please add option to not save OLE replacement objects
https://bugs.documentfoundation.org/show_bug.cgi?id=160915 Bug ID: 160915 Summary: Please add option to not save OLE replacement objects Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: junkyardma...@frontier.com Description: Saving OLE replacement objects tremendously increases the size of Calc workbook files and provides no benefit in most cases (not being linked or embedded by other applications). Steps to Reproduce: 1.Save Calc spreadsheet that contains charts. 2. 3. Actual Results: OLE replacement objects are included within the saved file. Expected Results: OLE replacement objects not included within the saved file. Reproducible: Always User Profile Reset: No Additional Info: In many, if not most cases, documents are not link or embedded by other documents/applications. Unnecessarily included OLE replacement objects is a waste of time, storage, memory, CPU, backup, etc. resources. Please implement an option to not include OLE replacement objects in the saved document file. Thanks -- You are receiving this mail because: You are the assignee for the bug.
[Bug 124116] Track-changes Hebrew & Arabic punctuation shifted from correct position on regular text
https://bugs.documentfoundation.org/show_bug.cgi?id=124116 --- Comment #11 from Eyal Rozenberg --- Created attachment 193943 --> https://bugs.documentfoundation.org/attachment.cgi?id=193943=edit Screenshot of the document as rendered in LO Writer 24.2.0.2 GTK3 Screenshot of the Writer document attachment 150012, rendered with: Version: 24.2.0.2 (X86_64) / LibreOffice Community Build ID: b1fd3a6f0759c6f806568e15c957f97194bbec8f CPU threads: 4; OS: Linux 6.6; UI render: default; VCL: gtk3 Locale: en-IL (en_IL); UI: en-US (with document page dimensions narrowed to reduce screenshot width) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160896] Cell Column & Row Base
https://bugs.documentfoundation.org/show_bug.cgi?id=160896
--- Comment #2 from NOYB ---
A "Row_Column_Base" option would be similar to the already existing "Base"
option that sets the default base {0|1} for arrays and would not break any
existing macros. The default behavior would remain 0 base. Just like it does
for the array base option.
There is a direct correlation to the spreadsheet rows and columns labeling in
the physical real world here. The spreadsheet rows and columns functions
follow this direct correlation with using one (1) base.
Using zero (0) base in macros to reference spreadsheet rows and columns is
inconsistent with the spreadsheet functions and creates confusion, error and
extra effort in development and troubleshooting.
When there is a direct correlation to a physical world counted item, such as
spreadsheet rows an columns, a one (1) base is appropriate and easier for
humans to work with. Computer applications are tools of humans and as such
they should accommodate humans, rather than humans accommodating computer
applications.
The argument that it has always been done that way or is done that way
elsewhere is weak status quo prevention of change for the betterment.
Please implement a rows columns base option. It won't hurt.
Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 102985] [META] Font bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102985 Eyal Rozenberg changed: What|Removed |Added Depends on||159950 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=159950 [Bug 159950] Offer to download missing fonts from relevant online sources (dynamically, after installation) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159950] Offer to download missing fonts from relevant online sources (dynamically, after installation)
https://bugs.documentfoundation.org/show_bug.cgi?id=159950 Eyal Rozenberg changed: What|Removed |Added Blocks||102985 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102985 [Bug 102985] [META] Font bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159950] Offer to download missing fonts from relevant online sources (dynamically, after installation)
https://bugs.documentfoundation.org/show_bug.cgi?id=159950 Eyal Rozenberg changed: What|Removed |Added Blocks||102985 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102985 [Bug 102985] [META] Font bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 113496] Open source font installer bundles on download webpage per locale
https://bugs.documentfoundation.org/show_bug.cgi?id=113496 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9950 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 96872] Make it more obvious that a font has been substituted (see comment 12)
https://bugs.documentfoundation.org/show_bug.cgi?id=96872 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9950 -- You are receiving this mail because: You are the assignee for the bug.
