[Libreoffice-bugs] [Bug 154702] UI: Background Cell Color Resetting

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154702

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||chris.hurren...@gmail.com

--- Comment #3 from Stéphane Guillou (stragu) 
 ---
*** Bug 157904 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157904] Customising toolbar - add secondary font colour button

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157904

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thank you for the report, Chris.

This is likely because of the fix for bug 154270 and its many duplicates (12
currently, so you can see it needed to be fixed).
According to bug 154702 comment 2, your use case was unfortunately never
intended to work, so you were relying on that "bug" for your workflow...

Marking as duplicate, but there might be a case for opening an enhancement
request to allow easy access to a couple of colours for such buttons?

*** This bug has been marked as a duplicate of bug 154702 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156486] Automatic Spell check faulty after language change (Swahili)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156486

Buovjaga  changed:

   What|Removed |Added

Summary|Automatic Spell check   |Automatic Spell check
   |faulty after language   |faulty after language
   |change  |change (Swahili)

--- Comment #4 from Buovjaga  ---
Works for me with
https://extensions.libreoffice.org/en/extensions/show/swahili-dictionary Your
example text gives me redlining for makarne, Zilisauhuliwa and zimekumbukwa. F7
Spelling dialog also works as expected.

Tested both by doing the language change from another language and by having
Swahili (Tanzania) as default language for documents.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157906] Named ranged are lost when we convert from ods to xlsx

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157906

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
This is a sheet-level named range. I believe this should be fixed in version
7.6.3 with the fix for bug 157318. You can test a pre-release to confirm:
https://dev-builds.libreoffice.org/pre-releases/

Thank you!

*** This bug has been marked as a duplicate of bug 157318 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156486] Automatic Spell check faulty after language change

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156486

Martin Tlustos  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #3 from Martin Tlustos  ---
Well, for me it still doesn't work. I also tried German to rule out that it's
not a problem with the Swahili spell checker, but it still makes problems.
F7 either gives empty results and shows "no language", or checks all text as
English, although it is formatted as Swahili. Changing the spell checking
language to Swahili works, but must be done after every single word.

Here is some of the text I use:

Zilitumika kwa makarne na makarne
Zilisauhuliwa baada ya dawa za kisasa kubuniwa
zimekumbukwa miaka ya hivi karibuni
siku hizi kuna utafiti sana kuhusu dawa hizo


System Info:
Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 60(Build:1)
CPU threads: 6; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+wayland)
Locale: en-US (en_US.UTF-8); UI: en-US
Ubuntu package version: 4:7.6.2~rc1-0ubuntu0.22.04.1~lo1
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 33603] Presenter notes should be available in normal view as a scrolling pane

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33603

--- Comment #42 from Tex2002ans  ---
A user, JiL, at the Collabora Forums recently requested this feature too:

-
https://forum.collaboraonline.com/t/inquiry-about-powerpoint-style-comments/2119

- - -

To get this feature in...

Google Slides, you can press:

- View > Show speaker notes

Powerpoint, you can press:

- View > Notes

or:

- Press "Notes" in the middle of the very bottom taskbar.

For Microsoft's instructions, see:

-
https://support.microsoft.com/en-us/office/add-speaker-notes-to-your-slides-26985155-35f5-45ba-812b-e1bd3c48928e

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157698] [META] Unify lockdown UX in the Options dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157698
Bug 157698 depends on bug 157838, which changed state.

Bug 157838 Summary: Unify lockdown behavior of Options dialog page Print
https://bugs.documentfoundation.org/show_bug.cgi?id=157838

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157837] Unify lockdown behavior of Options dialog View page

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157837

Balázs Varga (allotropia)  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157698] [META] Unify lockdown UX in the Options dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157698
Bug 157698 depends on bug 157837, which changed state.

Bug 157837 Summary: Unify lockdown behavior of Options dialog View page
https://bugs.documentfoundation.org/show_bug.cgi?id=157837

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157698] [META] Unify lockdown UX in the Options dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157698
Bug 157698 depends on bug 157702, which changed state.

Bug 157702 Summary: Unify lockdown behavior of Options dialog General page
https://bugs.documentfoundation.org/show_bug.cgi?id=157702

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157698] [META] Unify lockdown UX in the Options dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157698
Bug 157698 depends on bug 157700, which changed state.

Bug 157700 Summary: Unify lockdown behavior of Options dialog page User Data
https://bugs.documentfoundation.org/show_bug.cgi?id=157700

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157837] Unify lockdown behavior of Options dialog View page

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157837

Commit Notification  changed:

   What|Removed |Added

 Whiteboard||target:24.2.0

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157632] Can't set text direction via sidebar when object selected in Impress (not in edit mode)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157632

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Ever confirmed|0   |1
Summary|With multiple objects   |Can't set text direction
   |selected, can't set |via sidebar when object
   |direction via sidebar   |selected in Impress (not in
   ||edit mode)
Version|24.2.0.0 alpha0+ Master |5.4.0.3 release
 Status|UNCONFIRMED |NEW

--- Comment #4 from Stéphane Guillou (stragu) 
 ---
OK, I didn't have CTL turned on in Tools > Options > Languages. I can now see
those buttons, but you are right, they are greyed out when an object is
selected. They are only active when in edit mode.

Version: 5.4.0.3
Build ID: 92c2794a7c181ba4c1c5053618179937228ed1fb
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; 
Locale: en-AU (en_AU.UTF-8); Calc: group

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: fd69b546ad36452560cb11ccb28e78632d65f045
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157837] Unify lockdown behavior of Options dialog View page

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157837

--- Comment #4 from Commit Notification 
 ---
Balazs Varga committed a patch related to this issue.
It has been pushed to "master":

https://git.libreoffice.org/core/commit/bf7b0febbf3081a3693bf09bc4e779f7c6c30dc0

tdf#157837 - UI: Part 3 - Unify lockdown behavior of Options dialog

It will be available in 24.2.0.

The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
https://wiki.documentfoundation.org/Testing_Daily_Builds

Affected users are encouraged to test the fix and report feedback.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157906] Named ranged are lost when we convert from ods to xlsx

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157906

--- Comment #1 from nhatthinh.p...@iress.com ---
Created attachment 190396
  --> https://bugs.documentfoundation.org/attachment.cgi?id=190396&action=edit
Example to test the issue

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157906] New: Named ranged are lost when we convert from ods to xlsx

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157906

Bug ID: 157906
   Summary: Named ranged are lost when we convert from ods to xlsx
   Product: LibreOffice
   Version: 7.6.0.3 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: nhatthinh.p...@iress.com

Description:
Named ranged are lost when we convert from ods to xlsx.
I cannot replicate this issue in LibreOffice Calc version 7.5.7 or earlier.
This issue happens from version 7.6

Steps to Reproduce:
1. Open LibreOffice Calc and create a Named Ranged.
2. Save as *.ods file.
3. Close this file.
4. Open this file and save as *.xlsx e.g. test_named_ranged.xlsx
5. Close all files.
6. Open test_name_ranged.xlsx and check the Named Ranged in step 1 has been
lost.

Actual Results:
The Named Ranged has been lost.

Expected Results:
The Named Ranged should be kept.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
I cannot replicate this issue in LibreOffice Calc version 7.5.7 or earlier.
This issue happens from version 7.6

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 43959] Horizontal ruler updates bad when changing zoom level

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=43959

--- Comment #19 from Tex2002ans  ---
Still reproduce this in:

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157826] MariaDB, direct Connection, Windows-Server: Data could be read by Base through Tools → SQL, but not by the GUI (table, form …)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157826

--- Comment #7 from Petr Poruban  ---
I tested a modified version of the last daily builds. 

The data transfer is now correct. Everything is running briskly and I haven't
encountered any problems so far. 

Only comment: 
all unfilled dates in my form are implicitly filled with the minimum date range
i.e. 1.1.1900. 
When transferring via ODBC, the date fields remain blank when transferring to
the form from the same database. 
Would it still be possible to modify this? I.e. not to fill in for the date,
empty fields or null fields, to the minimum value, but leave them really empty. 
Thank you.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 70526] Provide startup time measurements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=70526

--- Comment #8 from Buovjaga  ---
(In reply to Khushi Gautam from comment #7)
> (In reply to Buovjaga from comment #6)
> > (In reply to Khushi Gautam from comment #5)
> > > I want to work on this issue, However, can you please tell me what this
> > > "profiling tinderbox" means?
> > 
> > It refers to this: https://ci.libreoffice.org/computer/centos7-callgrind/
> 
> Do we need to include testcase also besides tracking startup performance?

If you mean a unit test, it does not seem necessary to me. I don't know what
others think, but if you want to work on this, just go ahead instead of waiting
for a consensus. A test can always be added later.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls/crashes under Windows 11 with Norwegian locale when opening file dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157135

--- Comment #27 from Buovjaga  ---
(In reply to Buovjaga from comment #23)
> In bug 157074 it was reported that the bibisect version 7.6.3.0.0 does not
> show the problem. Just to double-check, if the problem was fixed in a later
> commit, people with the win64-7.6 repo could do
> 
> git checkout fb8b2651f68817b9d49c47d61b189e58cf1df9b9
> 
> to change to an older build that is closer to 7.6.2, which was reported (in
> duplicate bugs) to still have the problem. If the problem does not show even
> in that commit, then there is something different in the release builds vs.
> bibisect builds.

Odd and others affected: could you try this? The basic information about
bibisecting is in bug 157074 comment 20.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157218] Impress Portable: Sizeable files won't load/play

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157218

Buovjaga  changed:

   What|Removed |Added

 Ever confirmed|1   |0
   Hardware|x86-64 (AMD64)  |x86 (IA32)
 Status|REOPENED|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157218] Impress Portable: Sizeable files won't load/play

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157218

Daniel Collins  changed:

   What|Removed |Added

 Resolution|NOTOURBUG   |---
 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED

--- Comment #10 from Daniel Collins  ---
Requesting that this be reopened. The Portable Apps people are saying this is
intrinsically a Libre Office bug -- specifically, that these larger math files
crash the normal 32-bit Libre Office, in versions 7.6.1/7.6.2. Portable Apps
only echoes the 32-bit version of Libre Office which has this problem
(apparently, as I myself don't have the 32-bit version installed).

See observation to that effect here: https://portableapps.com/node/69361

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157820] Command line argument does not accept Windows \\?\ path prefix

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157820

--- Comment #8 from Bernd Wechner  ---
(In reply to Federico Gallo from comment #6)
> I actually don't know if Libreoffice provide the dialog or just call the
> file explorer (that seems to be the right thing to do nowadays at least on
> linux). I'm not even using Windows. 
> You don't have to provide that information if you don't want to, I'm not the
> person that will work on this

I think you misunderstand the bug. I am using LibreOffice on the command line.
I am not using the File Open dialog.

I did a quick test and long paths (over 256 chars) open fine with Open File
dialog box. Not a problem. But when you try and open one on the command line as
follows say:

CD MyVeryDeepLongDIr
"E:\Util\LibreOffice\LibreOfficeCalcPortable.exe" MyFIle

then LibreOffice pops up:

E:\Util\LibreOffice\Wideband freq response - ByRegionsAll - Sv nonAvg -
upward-facing transducer_transposed.CSV does not exist.

A totally bizarre thing to report. And if I try it with the full path as
delivered by the Explorer when I right-click and rhen click Copy as path, then
LibreOffice does nothing at all. The copied path (and so the one that Open With
is passed also by the explorer is prepended with "\\?\". If I remove that, and
try again, LibreOffice starts and loads the file.

Summary:

File Open dialog box is all good
Receiving paths from the command line is broken for long paths (>256 chars)
because of a prefix Windows provides to the path to indicate it is long, but
which is not understood by whatever method LibreOffice subsequently tries to
open same file.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157820] Command line argument does not accept Windows \\?\ path prefix

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157820

--- Comment #7 from Bernd Wechner  ---
The fix is simple. If on an MS-Windows system then:

1) Remove any prefix from a file path that is "\\?\UNC\"
2) Remove any prefix from a file path that is "\\?\"

In that order. That's what I do as a work around by opening it with this
Powershell script rather than with LibreOffice directly

Calc.ps1:
param(
[Parameter(Mandatory=$true)]
[string]$Path
)

[regex]$pattern1 = [regex]::Escape("\\?\UNC\")
$Path = $pattern1.replace($Path, "\\", 1)

[regex]$pattern2 = [regex]::Escape("\\?\")
$Path = $pattern2.replace($Path, "", 1)

& E:\Util\LibreOffice\LibreOfficeCalcPortable.exe "$Path"


(Note I keep a binary for Calc at
E:\Util\LibreOffice\LibreOfficeCalcPortable.exe)

And then I can associate that by using this registration file patch:

Calc.reg:
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\SystemFileAssociations\.csv\shell\OpenCSVwithCalc]
@="Open with Calc"

[HKEY_CLASSES_ROOT\SystemFileAssociations\.csv\shell\OpenCSVwithCalc\command]
@="powershell.exe -NonInteractive -WindowStyle Hidden -File
\"E:\\Util\\LibreOffice\\Calc.ps1\" \"%1\""

And no all is good for me, and my shortcut menu.

But the bug remains. To be reliably cross-platform all LibreOffice needs to do
is update its Windows file path handler (I presume it already handles Windows
and *nix paths differently if only because of the \ vs / difference, and the
reality of drive letters. Wherever Windows paths are handled, these prefixes
simply need to be stripped from the path before continuing (they are Windows
way of telling a client the path is long, but not valid parts of a path, and
one might rightly argue that is one silly way to communicate this).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157892] Spell-checking does not work

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157892

--- Comment #3 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157892] Spell-checking does not work

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157892

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157648] FORMATTING: Setting language for Selection/Paragraph/All text can't be shortcut

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157648

QA Administrators  changed:

   What|Removed |Added

 Ever confirmed|1   |0
 Status|NEEDINFO|UNCONFIRMED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157648] FORMATTING: Setting language for Selection/Paragraph/All text can't be shortcut

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157648

--- Comment #5 from QA Administrators  ---
[Automated Action] NeedInfo-To-Unconfirmed

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154382] Very slow program

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154382

QA Administrators  changed:

   What|Removed |Added

 Resolution|--- |INSUFFICIENTDATA
 Status|NEEDINFO|RESOLVED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 117462] FORMATING: Rendering of svg file (LO-Logo) is incorrect and corrupt after rotation

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117462

--- Comment #14 from QA Administrators  ---
Dear Micha,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 74533] EDITING hyperlink: column insert after hidden column with hyperlins creates a column with invisible and undelettable hyperlinks

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=74533

--- Comment #11 from QA Administrators  ---
Dear Andrew,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108371] Query design edits are lost when next clicking in any field selector box.

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108371

--- Comment #8 from QA Administrators  ---
Dear Howard Johnson,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 154382] Very slow program

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=154382

--- Comment #3 from QA Administrators  ---
Dear Luiz,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 106297] Paste special MS Word .doc to Writer only pastes the first page

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=106297

--- Comment #5 from QA Administrators  ---
Dear Marco A.G.Pinto,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed
bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this
bug report. During that time, it's possible that the bug has been fixed, or the
details of the problem have changed. We'd really appreciate your help in
getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice
from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information
from Help - About LibreOffice.

If the bug is NOT present, please set the bug's Status field to
RESOLVED-WORKSFORME and leave a comment that includes the information from Help
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your
bug pertains to a feature added after 3.3) from
https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat:
https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157905] New: PIVOTTABLE Edit Style not working

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157905

Bug ID: 157905
   Summary: PIVOTTABLE Edit Style not working
   Product: LibreOffice
   Version: 7.6.2.1 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: l13h...@gmail.com

Created attachment 190395
  --> https://bugs.documentfoundation.org/attachment.cgi?id=190395&action=edit
edit pivot table value style

i have change style in pivot table (Pivot table value edit Numbers - thousands
separator)
when i accept it in my pivottable not working (in case my data without number
formating)

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 152534] Win11 dark theme support--Active selections have light blue background which makes white icons and text almost invisible

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=152534

--- Comment #31 from nzotfh...@mozmail.com ---
I can confirm that (In reply to WildByDesign from comment #26)
> The developer of Explorer++, David Erceg, who has a good understanding of
> the win32-darkmode implementations has followed up with a nicely detailed
> response.
> 
> Link:
> https://github.com/derceg/explorerplusplus/issues/115#issuecomment-1666308914
> 
> Some of my takeaways from the response:
> 
> - The issue is not likely specific to the aero.msstyles theme resource file
> itself, but more likely issues within the dark mode API (within Windows)
> that pulls data from the theme resource file.
> 
> - "Even with the use of the undocumented APIs and classes from
> aero.msstyles, partially or fully drawing controls is still necessary to
> achieve a cohesive result."
> 
> - The fact that win32-darkmode consists of undocumented APIs, these issues
> would be unsupported and extremely unlikely that Microsoft would ever fix
> these issues.
> 
> Since Microsoft requires installing an app just to vote for the issue to be
> fixed, that makes it much more difficult to bring attention to the issue.
> There is often issues in Windows which get 10s of thousands of votes before
> it puts enough pressure on Microsoft to implement whatever fix or feature
> update. I don't hold much hope on this issue, unfortunately.
> 
> Also, from my own personal opinion, that workaround that Notepad++ which
> simply inverts the color, is still quite terrible. That workaround would
> still be bad for any users with vision problems. Also it's quite jarring
> regardless from a visual perspective.
> 
> I created an msstyles alternative
> (https://github.com/WildByDesign/Aero.msstyles-win32-darkmode) which is
> essentially default aero.msstyles file with the one and only change to it
> being swapping the terrible bright blue highlight to a proper dark mode
> highlight for toolbar icons. Yet still, getting users to install a separate
> aero.msstyles theme is not a great workaround either. I created this mostly
> with vision impaired users in mind.
> 
> I still believe that custom drawing the toolbar icons is the only proper way
> to fix this bug and it seems to be what David Erceg (Explorer++ dev) is also
> suggesting.

Thanks WildByDesign, your solution on GitHub works great! I'm not sure what the
best place would be, but it'd be great if this was also linked in the official
support somewhere or anywhere more obvious -- it the only way I've found to
make Windows 11 dark mode usable and it took some *finding*.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157904] New: Customising toolbar - add secondary font colour button

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157904

Bug ID: 157904
   Summary: Customising toolbar - add secondary font colour button
   Product: LibreOffice
   Version: 7.6.2.1 release
  Hardware: All
   URL: https://ask.libreoffice.org/t/customising-toolbar-add-
secondary-font-colour-button/97348
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: LibreOffice
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: chris.hurren...@gmail.com

Prior to updating LibreOffice to 7.6.2.x (i.e. I had LO 7.5.x.x), I was able to
add and use 2 font colour buttons and 2 background colour buttons in the
formatting toolbar so that I can set different colours (for each
element/button) for quick convenience. But as I have upgraded to 7.6.2.1, this
functionality is no longer possible. Undesired behaviour - scenario example: If
I choose and apply a font colour in one font colour button, the other font
colour button changes too to match the first font colour button! It wasn’t the
case prior to LO 7.6.2.1. I wanted the other font colour button to remain as it
is.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 149077] Change how Rounded Rectangle Callout is drawn in LibreOffice

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=149077

--- Comment #9 from Khushi Gautam  ---
(In reply to Regina Henschel from comment #7)
> What do you already know about custom shapes? Do you know, how the ODF
> markup in file is written? Do you know how the information is hold in
> property CustomShapeGeometry (Development Tools)? Do you now how shapes were
> defined in VML? Do you know "limo stretch" or "stretchpoint"? Then I would
> know where to start to explain the mso_CustomShape struct. Should we discuss
> it in direct mails? Or we start a Wiki-page about this topic? I think it is
> a little bit off-topic for Bugzilla.

I want to know about how the shapes are defined in VML, Also if I am making any
changes in the EnhancedCustomShapeGeometry.cxx , will the changed reflect in
impress document or draw document. Also whenever I am editing
"msoWedgeRRectCallout" I am unable to see any differences. Just wants to know
from where this shape is coded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157903] New: Cannot assign special symbols to keys

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157903

Bug ID: 157903
   Summary: Cannot assign special symbols to keys
   Product: LibreOffice
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: onor...@online.no

Description:
I am writing a text that uses both Norwegian and Icelandic letters. For the
Icelandic letters, I use the convention of entering the Unicode number followed
by Alt-X, e.g. Þ = 0DE Alt-X
It would be a great enhancement if it were possible to define that as a kind of
macro and assign it to a key, e.g. "AltGr-T := 0DE Alt-X"

Steps to Reproduce:
1. In Writer, select assign value to a key
2. Enter the desired string
3. Choose the key to represent that string

Actual Results:
It only works for predefined macros, not for character strings.

Expected Results:
Not yet possible.


Reproducible: Always


User Profile Reset: No

Additional Info:
It would be nice if the software asked if I want to make the assignment just
for the current document, or generally for all documents.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157612] Calc blank digit ('?') format have the wrong width

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157612

--- Comment #6 from Mike Kaganski  ---
(In reply to Stéphane Guillou (stragu) from comment #5)
> (In reply to Vincent Boudry from comment #4)
> 
> Direct link:
> https://help.libreoffice.org/7.6/en-US/text/shared/01/05020301.
> html#hd_id3154330
> 
> why couldn't the same mechanics be used here?

I agree that it is likely reasonable and doable.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108720] Do not render previews of symbol fonts

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108720

V Stuart Foote  changed:

   What|Removed |Added

 CC||kha...@libreoffice.org

--- Comment #14 from V Stuart Foote  ---
as in comment 12, refactoring suggested comment 4 not yet in place.

@Khaled, any interest?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls/crashes under Windows 11 with Norwegian locale when opening file dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157135

--- Comment #26 from Odd Nordland  ---
(In reply to Odd Nordland from comment #25)
> (In reply to Odd Nordland from comment #24)
> > (In reply to Odd Nordland from comment #16)
> > > (In reply to Buovjaga from comment #15)
> > > > Noticing Mike's addition to See Also, wow, looks like we have a 
> > > > Norwegian
> > > > connection!
> > > > 
> > > > Bug 157564: "The error is not reproduced in Windows US version, where 
> > > > the
> > > > Writer document behaves normally."
> > > 
> > > Asyou can see from my original bug report, I am also using Norwegian, both
> > > for Windows 10 and 11. I'll give the portable version of LibreOffice 7.6 a
> > > try on my wife's computer, which is running in German!
> > 
> > I have now tried out the portable version of LibreOffice under UK English,
> > German, Danish, Swedish and Norwegian versions of Windows 10. In all cases,
> > the User Interface and Locale for LibreOffice were set to Norwegian.
> > LibreOffice only stalls in the Norwegian environment.
> > I notice that I can open a spreadsheet into Calc, but then LibreOffice
> > stalls. Trying to open a text file for Writer stalls immediately.
> > 
> > The LibreOffice version I have done the tests with is
> > Version: 7.6.0.3 (x86) / LibreOffice Community
> > Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
> > CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL:
> > win
> > Locale: nb-NO (nb_NO); UI: nb-NO
> > Calc: threaded
> 
> N6te that the above mentioned version of Libre Office Portable is what you
> get when you install using
> LibreOfficePortable_7.6.2_MultilingualStandard.paf.exe.
> I probably have to install the "hard disk" version to get version 7.6.2 or
> newer ...

I now installed
Version: 7.6.2.1 (x86) / LibreOffice Community
Build ID: 56f7684011345957bbf33a7ee678afaf4d2ba333
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: nb-NO (nb_NO); UI: nb-NO
Calc: threaded

Calc works, but Writer still stalls when opening a file.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 33201] UI: Highlight (not select) current row and column in spreadsheet

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=33201

Aml  changed:

   What|Removed |Added

   Assignee|amlhassanabdelhamid@gmail.c |libreoffice-b...@lists.free
   |om  |desktop.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157853] Unify lockdown behavior of Options dialog page Advanced

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157853

raal  changed:

   What|Removed |Added

Version|24.2.0.0 alpha0+ Master |5.4.0.3 release
 Ever confirmed|0   |1
 CC||r...@post.cz
 Status|UNCONFIRMED |NEW

--- Comment #2 from raal  ---
Confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3649dc202bedf72e37c77993a1f7027bfdfc6d9e
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

Version: 5.4.0.0.beta2+
Build ID: 721efbeb117962e9b0cd547b51ede4a6736042a6
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3; 
Locale: cs-CZ (cs_CZ.UTF-8); Calc: group

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls/crashes under Windows 11 with Norwegian locale when opening file dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157135

--- Comment #25 from Odd Nordland  ---
(In reply to Odd Nordland from comment #24)
> (In reply to Odd Nordland from comment #16)
> > (In reply to Buovjaga from comment #15)
> > > Noticing Mike's addition to See Also, wow, looks like we have a Norwegian
> > > connection!
> > > 
> > > Bug 157564: "The error is not reproduced in Windows US version, where the
> > > Writer document behaves normally."
> > 
> > Asyou can see from my original bug report, I am also using Norwegian, both
> > for Windows 10 and 11. I'll give the portable version of LibreOffice 7.6 a
> > try on my wife's computer, which is running in German!
> 
> I have now tried out the portable version of LibreOffice under UK English,
> German, Danish, Swedish and Norwegian versions of Windows 10. In all cases,
> the User Interface and Locale for LibreOffice were set to Norwegian.
> LibreOffice only stalls in the Norwegian environment.
> I notice that I can open a spreadsheet into Calc, but then LibreOffice
> stalls. Trying to open a text file for Writer stalls immediately.
> 
> The LibreOffice version I have done the tests with is
> Version: 7.6.0.3 (x86) / LibreOffice Community
> Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
> CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL:
> win
> Locale: nb-NO (nb_NO); UI: nb-NO
> Calc: threaded

N6te that the above mentioned version of Libre Office Portable is what you get
when you install using LibreOfficePortable_7.6.2_MultilingualStandard.paf.exe.
I probably have to install the "hard disk" version to get version 7.6.2 or
newer ...

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157854] Unify lockdown behavior of Options dialog page Proxy

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157854

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||r...@post.cz

--- Comment #2 from raal  ---
> Here the fields are greyed out, but they lack lock icons to indicate their
> state.

Confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3649dc202bedf72e37c77993a1f7027bfdfc6d9e
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157901] Crash when I try to copy any cell that contains a formula

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157901

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 Ever confirmed|0   |1
 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thanks for the report.
LO 7.4 won't see further updates. Can you please test again in a recent
version, preferable 7.6?
Thank you!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107575] [META] Number format bugs and enhancements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107575

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on||157612


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157612
[Bug 157612] Calc blank digit ('?') format have the wrong width
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157612] Calc blank digit ('?') format have the wrong width

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157612

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   Keywords||needsDevAdvice
 Blocks||107575
   Severity|normal  |enhancement
 Status|UNCONFIRMED |NEW
 CC||mikekagan...@hotmail.com,
   ||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1
 OS|macOS (All) |All

--- Comment #5 from Stéphane Guillou (stragu) 
 ---
(In reply to Vincent Boudry from comment #4)
> (see Spaces on
> file:///Applications/Editing/LibreOffice7.6.2.app/Contents/Resources/help/en-
> US/text/shared/01/05020301.html?&DbPAR=CALC&System=MAC)

Direct link:
https://help.libreoffice.org/7.6/en-US/text/shared/01/05020301.html#hd_id3154330

I only realise now that Calc aligns digits regardless of if the font used is
monospace or not. (Easily visible when comparing some right-aligned numbers
using Liberation Sans Narrow in Calc vs Writer.)

Mike, I obviously know nothing about how it is implemented, but why couldn't
the same mechanics be used here? (Keep the space character that is already
used, but with the extra padding that results in having the same width as all
other digits.)

In any case, agreeing that the display should be improved, but making this an
enhancement request.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107575
[Bug 107575] [META] Number format bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157135] LibreOffice 7.6 stalls/crashes under Windows 11 with Norwegian locale when opening file dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157135

--- Comment #24 from Odd Nordland  ---
(In reply to Odd Nordland from comment #16)
> (In reply to Buovjaga from comment #15)
> > Noticing Mike's addition to See Also, wow, looks like we have a Norwegian
> > connection!
> > 
> > Bug 157564: "The error is not reproduced in Windows US version, where the
> > Writer document behaves normally."
> 
> Asyou can see from my original bug report, I am also using Norwegian, both
> for Windows 10 and 11. I'll give the portable version of LibreOffice 7.6 a
> try on my wife's computer, which is running in German!

I have now tried out the portable version of LibreOffice under UK English,
German, Danish, Swedish and Norwegian versions of Windows 10. In all cases, the
User Interface and Locale for LibreOffice were set to Norwegian.
LibreOffice only stalls in the Norwegian environment.
I notice that I can open a spreadsheet into Calc, but then LibreOffice stalls.
Trying to open a text file for Writer stalls immediately.

The LibreOffice version I have done the tests with is
Version: 7.6.0.3 (x86) / LibreOffice Community
Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265
CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: nb-NO (nb_NO); UI: nb-NO
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157614] Contextual menus span over 2 screens making them difficult to read

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157614

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDINFO
 CC||stephane.guillou@libreoffic
   ||e.org
 Ever confirmed|0   |1
 Whiteboard| QA:needsComment|

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thank you for the report. Version 6.4 is not supported anymore. Can you please:
- install a supported version: https://www.libreoffice.org/download/download/
- test again
- if the issue persists, please check that it is not already covered in one of
these reports:
https://bugs.documentfoundation.org/showdependencytree.cgi?id=104160&hide_resolved=1
- if not, please also attach a screenshot of the issue.

Much appreciated!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157885] help png images could use indexed colours

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157885

--- Comment #3 from Jérôme  ---
The images are in the following directories :
help/media/helpimg
help/media/screenshots

The png image are :
- in the main tree (main MSI archive on Windows)
- in each translation sub-directories (each translated help MSI archive on
Windows).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143988] The menu is not being displayed in Calc when using the tabbed user interface with two monitors

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143988

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||stephane.guillou@libreoffic
   ||e.org

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
seven, which menu exactly are you talking about?
Do you still see the same issue in a recent version?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 70526] Provide startup time measurements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=70526

--- Comment #7 from Khushi Gautam  ---
(In reply to Buovjaga from comment #6)
> (In reply to Khushi Gautam from comment #5)
> > I want to work on this issue, However, can you please tell me what this
> > "profiling tinderbox" means?
> 
> It refers to this: https://ci.libreoffice.org/computer/centos7-callgrind/

Do we need to include testcase also besides tracking startup performance?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157899] open last session's documents (almost implemented already)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157899

Mike Kaganski  changed:

   What|Removed |Added

URL||https://wiki.documentfounda
   ||tion.org/ReleaseNotes/7.6#G
   ||UI

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157899] open last session's documents (almost implemented already)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157899

--- Comment #2 from Mike Kaganski  ---
(In reply to peter josvai from comment #0)
> Unlike before, now there is a line separating the last session's files from
> the rest (of the document history)... (!! :)) 

No. The line separates not the last session's documents, but 5 last documents
of this component (e.g., Writer's, when you work in Writer) from the rest
(Calc's, Impress', etc.). They will be 5, no matter how many documents were
open last time, and in what modules.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153527] LibreOffice 7.5 Calc: unable to apply formatting to all cells in spreadsheet

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153527

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||7902

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157902] INCONSISTENT FORMATTING IN CALC

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157902

Mike Kaganski  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3527

--- Comment #1 from Mike Kaganski  ---
Likely a dupe of bug 153527?

But the "ONLY the 'selected' cells get the NEW formatting" confuses me: so are
you selecting some part of sheet, and expect other parts be formatted? Or is
your issue that you select everything, but only non-empty (not "selected")
cells get the formatting?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157897] Calc: linked files adding print ranges with each update

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157897

Andreas Heinisch  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|libreoffice-b...@lists.free |andreas.heini...@yahoo.de
   |desktop.org |

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157897] Calc: linked files adding print ranges with each update

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157897

--- Comment #3 from Andreas Heinisch  ---
Yep, the cause for this issue is bug 66613. I will provide a fix.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 111843] one active cell selection is not searched with "Current selection only" option set in Find & Replace dialog tool

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=111843

--- Comment #12 from John Smith  ---
I have encountered an issue with the "Find & Replace" tool in LibreOffice Calc.
When attempting to use the "Current selection only" option after clicking on a
single cell (the active cell), the tool does not find the search criteria, even
if it exists in the active cell.

In my opinion, an active cell should be considered a "current selection," as it
is the cell I have interacted with and is the starting point for the search
operation. It is not intuitive that this does not work as expected.

I have observed that when the active cell contains content, the "Current
selection only" option is selectable, but when the active cell is empty, the
option is grayed out. This distinction implies that the tool recognizes the
active cell's content status, just like it does for cell ranges.

ref: https://thestyledare.com/product/granite-slab/van-gogh/

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157687] Calc : all rows crossed out instead of a single row

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157687

severine...@yahoo.fr changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #14 from severine...@yahoo.fr ---
merci à tous les deux. 
Je ne peux pas fournir une série d'étapes pour reproduire le bug car je n'en ai
aucune idée. 
J'ai tenté de le reproduire mais ce n'est pas arrivé. 
Grace à vous je devrais désormais avoir des sauvegardes automatiques. Je
vérifierais
Merci pour votre aide.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports and tasks

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143781

BogdanB  changed:

   What|Removed |Added

 Depends on||125718


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=125718
[Bug 125718] Regression in TDF deb packaging: from 6.2, libreoffice executable
has been moved to /usr/local
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 125718] Regression in TDF deb packaging: from 6.2, libreoffice executable has been moved to /usr/local

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125718

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||143781


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=143781
[Bug 143781] [META] Development- and code-related bug reports and tasks
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 143781] [META] Development- and code-related bug reports and tasks

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=143781

BogdanB  changed:

   What|Removed |Added

 Depends on||156443


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=156443
[Bug 156443] Windows: alt+numpad doesn't work for Unicode decimal codes, like
in WordPad/Word
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 156443] Windows: alt+numpad doesn't work for Unicode decimal codes, like in WordPad/Word

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=156443

BogdanB  changed:

   What|Removed |Added

 Blocks||143781
 CC||buzea.bog...@libreoffice.or
   ||g


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=143781
[Bug 143781] [META] Development- and code-related bug reports and tasks
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157897] Calc: linked files adding print ranges with each update

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157897

tmacalp  changed:

   What|Removed |Added

 CC||tmac...@gmail.com
 Status|UNCONFIRMED |NEW
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=66
   ||613
Version|7.5.7.1 release |7.5.3.2 release
 Ever confirmed|0   |1

--- Comment #2 from tmacalp  ---
Confirming and marking as NEW.

I don't have a bibsect environment installed, but I've at least tracked it to
not affecting 7.5.2, but affecting 7.5.3.  I changed the "earliest affected
version" to 7.5.3.2.  

I also searched and found bug 66613, which is likely when this bug was
introduced, so I've placed a see-also for that report.

I won't mess with the importance, but it's a regression, so it should probably
be adjusted.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 108741] [META] Shapes bugs and enhancements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108741

BogdanB  changed:

   What|Removed |Added

 Depends on||157894


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157894
[Bug 157894] Undesirable rendering of dashed line in shapes with corners
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157894] Undesirable rendering of dashed line in shapes with corners

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157894

BogdanB  changed:

   What|Removed |Added

 Blocks||108741


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108741
[Bug 108741] [META] Shapes bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104848] [META] DOC (binary) file opening issues

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104848

BogdanB  changed:

   What|Removed |Added

 Depends on||119079


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=119079
[Bug 119079] FILEOPEN DOC: character properties affecting CR, but shouldn't
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 119079] FILEOPEN DOC: character properties affecting CR, but shouldn't

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=119079

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||104848


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=104848
[Bug 104848] [META] DOC (binary) file opening issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157594] FILEOPEN: DOC: layout is broken because of inline image (should be floating) in specific, broken doc

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157594

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||104848


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=104848
[Bug 104848] [META] DOC (binary) file opening issues
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 104848] [META] DOC (binary) file opening issues

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104848

BogdanB  changed:

   What|Removed |Added

 Depends on||157594


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157594
[Bug 157594] FILEOPEN: DOC: layout is broken because of inline image (should be
floating) in specific, broken doc
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103512] [META] AutoFilter-related bugs and enhancements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103512

BogdanB  changed:

   What|Removed |Added

 Depends on||157878


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157878
[Bug 157878] AUTOFILTER : Doesn't work with 2 words like "CP" and "Mi-CP" or
"MiCP"
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157878] AUTOFILTER : Doesn't work with 2 words like "CP" and "Mi-CP" or "MiCP"

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157878

BogdanB  changed:

   What|Removed |Added

 CC||buzea.bog...@libreoffice.or
   ||g
 Blocks||103512


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=103512
[Bug 103512] [META] AutoFilter-related bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157902] New: INCONSISTENT FORMATTING IN CALC

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157902

Bug ID: 157902
   Summary: INCONSISTENT FORMATTING IN CALC
   Product: LibreOffice
   Version: 3.3.0 release
  Hardware: Other
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: n...@grumpie.ca

Description:
When formatting a Spreadsheet, ONLY the 'selected' cells get the NEW
formatting.  All the cells in a spreadsheet should be the NEW Format.  If only
a few cell should be re-formatted, then selecting them BEFORE the Re-Format
should restrict the change to these cells ONLY.

Keep up the Good Work,

Ciao

Actual Results:
Entering data in an 'unused' Calc cell, defaults to 10 pt text height!

Expected Results:
Should be the SAME as the selected test height selected for the Currently
Occupied Cells.


Reproducible: Always


User Profile Reset: No

Additional Info:
Maintain a CONSISTENT Text Formatting (except of previously SPECIALLY Formatted
Cells).

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157859] Unify lockdown behavior of Options dialog page Load/Save - General

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157859

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||r...@post.cz

--- Comment #2 from raal  ---
Confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3649dc202bedf72e37c77993a1f7027bfdfc6d9e
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

I can reproduce the crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157860] Unify lockdown behavior of Options dialog page Load/Save - VBA Properties

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157860

raal  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever confirmed|0   |1
 CC||r...@post.cz

--- Comment #2 from raal  ---
Confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3649dc202bedf72e37c77993a1f7027bfdfc6d9e
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

I can not reproduce the crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157861] Unify lockdown behavior of Options dialog page Load/Save - MS Office

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157861

raal  changed:

   What|Removed |Added

 CC||r...@post.cz
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #2 from raal  ---
Confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3649dc202bedf72e37c77993a1f7027bfdfc6d9e
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

I can reproduce the crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157862] Unify lockdown behavior of Options dialog page Load/Save - HTML

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157862

raal  changed:

   What|Removed |Added

 CC||r...@post.cz
 Ever confirmed|0   |1
 Status|UNCONFIRMED |NEW

--- Comment #2 from raal  ---
Confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 3649dc202bedf72e37c77993a1f7027bfdfc6d9e
CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3
Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US
Calc: threaded

I can reproduce the crash.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 87892] More shapes for LibreOffice draw are needed

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87892

Emily Heaton  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |eaheat...@gmail.com
   |desktop.org |

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157839] Unify lockdown behavior of Options dialog page Fonts

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157839

Balázs Varga (allotropia)  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |balazs.varga...@gmail.com
   |desktop.org |
 Status|NEW |ASSIGNED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 153360] Languagetool 7.4 not working with languages different from default language (Languagetool installed from Preferences)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153360

Timur  changed:

   What|Removed |Added

   Hardware|ARM |All
 OS|macOS (All) |All

--- Comment #19 from Timur  ---
This is a major issue. LO built LT is not usable in mixed language paragraphs.
OK with LT extension.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 107817] [META] Impress UI/UX bugs and enhancements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=107817
Bug 107817 depends on bug 111737, which changed state.

Bug 111737 Summary: Not possible to create / add a new Master Slide with 
pressing Enter in slides/pages pane
https://bugs.documentfoundation.org/show_bug.cgi?id=111737

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 102283] [META] Slide/page pane bugs and enhancements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102283
Bug 102283 depends on bug 111737, which changed state.

Bug 111737 Summary: Not possible to create / add a new Master Slide with 
pressing Enter in slides/pages pane
https://bugs.documentfoundation.org/show_bug.cgi?id=111737

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 103152] [META] Writer image bugs and enhancements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=103152

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|157617  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157617
[Bug 157617] Inserting paragraph marks after a picture go unexpectedly
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 87740] [META] Anchor and text wrapping bugs and enhancements

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87740

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Depends on|157617  |


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=157617
[Bug 157617] Inserting paragraph marks after a picture go unexpectedly
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146445] Change behaviour of anchor to character in an empty paragraph (see comment 15)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146445

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=15 |
   |7617|
 CC||adalbert.hans...@gmx.de

--- Comment #46 from Stéphane Guillou (stragu) 
 ---
*** Bug 157617 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157617] Inserting paragraph marks after a picture go unexpectedly

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157617

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks|87740, 103152   |
   See Also|https://bugs.documentfounda |
   |tion.org/show_bug.cgi?id=14 |
   |6445|
 Resolution|--- |DUPLICATE
 Status|UNCONFIRMED |RESOLVED
Version|24.2.0.0 alpha0+ Master |7.2.0.4 release

--- Comment #2 from Stéphane Guillou (stragu) 
 ---
Thank you both!

The paragraph-anchored picture following the new paragraph didn't use to happen
back in 6.4

Reproduced in:

Version: 7.2.0.4 / LibreOffice Community
Build ID: 9a9c6381e3f7a62afc1329bd359cc48accb6435b
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

Not reproduced in 7.1.

So this is the fix for bug 120469, which is already mentioned in bug 146445
comment 3.

Let's mark as duplicate of bug 146445, which catches the general discontent
with this.

*** This bug has been marked as a duplicate of bug 146445 ***


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=87740
[Bug 87740] [META] Anchor and text wrapping bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103152
[Bug 103152] [META] Writer image bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157901] New: Crash when I try to copy any cell that contains a formula

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157901

Bug ID: 157901
   Summary: Crash when I try to copy any cell that contains a
formula
   Product: LibreOffice
   Version: 7.4.7.2 release
  Hardware: All
OS: macOS (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: gann...@gmail.com

Description:
When I try to copy/paste a formula, frequent (approx 20%) crash as soon as I
hit Copy.

Steps to Reproduce:
1.select a cell that contains a formula, that you want to duplicate
2.hit Command+C to copy
3.

Actual Results:
immediate crash

Expected Results:
well... copy the cell content and stay alive, I presume...


Reproducible: Sometimes


User Profile Reset: No

Additional Info:
Version: 7.4.7.2 / LibreOffice Community
Build ID: 723314e595e8007d3cf785c16538505a1c878ca5
CPU threads: 4; OS: Mac OS X 13.4.1; UI render: default; VCL: osx
Locale: fr-FR (fr_FR.UTF-8); UI: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 146769] Reopen documents from previous session on start

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=146769

--- Comment #19 from Stéphane Guillou (stragu) 
 ---
*** Bug 157899 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157899] open last session's documents (almost implemented already)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157899

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Thanks for the suggestion, Peter. This issue is already tracked in bug 146769,
so marking as a duplicate. Comments are welcome there.
Much appreciated!

*** This bug has been marked as a duplicate of bug 146769 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157900] New: OGLtrans don't work on Libreoffice Impress with QT/KDE backend

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157900

Bug ID: 157900
   Summary: OGLtrans don't work on Libreoffice Impress with QT/KDE
backend
   Product: LibreOffice
   Version: 7.6.2.1 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Impress
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: guido.iod...@gmail.com

Using QT5, QT6 or Kf5 backends, OpenGL transitions do not work. By contrast,
using gtk3, gtk4 or gen they work.

Version: 7.6.2.1 (X86_64) / LibreOffice Community
Build ID: 60(Build:1)
CPU threads: 8; OS: Linux 6.6; UI render: default; VCL: kf5 (cairo+xcb)
Locale: it-IT (it_IT.UTF-8); UI: it-IT
7.6.2-3
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157896] CALC: VLOOKUP can't find numbers formatted as text by import dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157896

Eike Rathke  changed:

   What|Removed |Added

 Status|RESOLVED|CLOSED

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157896] CALC: VLOOKUP can't find numbers formatted as text by import dialog

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157896

Eike Rathke  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

--- Comment #2 from Eike Rathke  ---
Not a bug. VLOOKUP() is defined to lookup _matching_ values. A numeric value
does not match a text value.

Also note that a leading ' apostrophe you might see in the Input Line or while
editing a cell is not part of the cell content and does not influence a lookup.
It indicates that the input could be interpreted as a number if it was entered
without the apostrophe in a cell formatted as numeric, and with apostrophe will
be entered as text content. Editing such content means it was already entered
as text.
See also
https://help.libreoffice.org/7.6/en-GB/text/scalc/guide/text_numbers.html?&DbPAR=CALC
and
https://help.libreoffice.org/7.6/en-GB/text/scalc/guide/integer_leading_zero.html?&DbPAR=CALC

Your sample document does not contain such scenario though, because the cell
range A1:A8 is formatted as Text, not numeric.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157848] XML Form Document: Binding of field with ":" won't work - needed for electronic invoices

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157848

--- Comment #7 from Robert Großkopf  ---
Created attachment 190392
  --> https://bugs.documentfoundation.org/attachment.cgi?id=190392&action=edit
Example for exported xml-code with namspaces

Have added an example for the exported *.xml-file, which should also be
exported by LibreOffice. I have exported this by using StarBasic Macros and a
Writer file, will use it also by export from Base. 
For an allround solution it would be good to use XML-Forms, which should use
this possibilities by default.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157889] Highlight is nearly impossible to remove in WPS or MSWord when applied in Libre Writer.

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157889

Don  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |NOTABUG

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157889] Highlight is nearly impossible to remove in WPS or MSWord when applied in Libre Writer.

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157889

--- Comment #2 from Don  ---
(In reply to Telesto from comment #1)
> (In reply to Don from comment #0) 
> > It would seem L.O. Writer uses the CharBackgroundColor property, whereas the
> > other programs use CharHighlight property.
> 
> True. For some background on the matter: bug 125268

Thank you Telesto. I understand the reasoning behind this now. I think I will
close this bug as there isn't a "cure-all" fix from the looks of it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157899] New: open last session's documents (almost implemented already)

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157899

Bug ID: 157899
   Summary: open last session's documents (almost implemented
already)
   Product: LibreOffice
   Version: 24.2.0.0 alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: j...@cspv.hu

hi, 


When we open Writer, we see the last opened / closed (?) documents' titles in
the "recent files" list

Unlike before, now there is a line separating the last session's files from the
rest (of the document history)... (!! :)) 

>From here it is just one further step to give us an option:
open the last session's files" :)

I mean, now Libreoffice knows which files they are...
they are identified...

Why not offer it for opening? Even from context menu...?

I'm sure people using Libreoffice would love that!


- - - - thank you for developing Writer! - - - -

-- 
You are receiving this mail because:
You are the assignee for the bug.

[Libreoffice-bugs] [Bug 157898] New: MariaDB JDBC-Connection: Values in query, connected to two tables, will be duplicated while moving cursor

2023-10-23 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=157898

Bug ID: 157898
   Summary: MariaDB JDBC-Connection: Values in query, connected to
two tables, will be duplicated while moving cursor
   Product: LibreOffice
   Version: 7.6.2.1 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Base
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: rob...@familiegrosskopf.de

This bug is a special bug of MariaDB with JDBC in LO Base:

Create two tables with the following code in MariaDB:
–

CREATE TABLE `Person` (
  `ID` tinyint(3) NOT NULL,
  `Forename` varchar(100) DEFAULT NULL,
  `Surname` varchar(100) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
CREATE TABLE `Zensuren` (
  `PersonID` tinyint(3) NOT NULL,
  `F1` tinyint(3) UNSIGNED DEFAULT NULL,
  `F2` tinyint(3) UNSIGNED DEFAULT NULL,
  `F3` tinyint(3) UNSIGNED DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_general_ci;
ALTER TABLE `Person`
  ADD PRIMARY KEY (`ID`);
ALTER TABLE `Zensuren`
  ADD PRIMARY KEY (`PersonID`);
ALTER TABLE `Person`
  MODIFY `ID` tinyint(3) NOT NULL AUTO_INCREMENT;
ALTER TABLE `Zensuren`
  ADD CONSTRAINT `Zensuren_ibfk_1` FOREIGN KEY (`PersonID`) REFERENCES `Person`
(`ID`) ON DELETE CASCADE ON UPDATE CASCADE;

–-
Insert some values in table "Person". Only one character for Forname will be
enough.
Insert the same values for ID as created in "Person" into "PersonID".
Connect both tables in a query.
Only with JDBC-connection you will be able to add values to F1, F2 and F3.
(Write protected with direct connection - don't know why).
Add '2' in first row of F1.
Move arrow down to next row.
'2' will be shown in next row.
Move down again.
'2' will move with the cursor.

Seems something is going wrong with refreshing when changing to next row.

All detected in LO 7.6.2.1, might be also in older versions. Seems to work well
with AOO - so not a bug of JDBC-connection …

-- 
You are receiving this mail because:
You are the assignee for the bug.

  1   2   3   >