[Libreoffice-bugs] [Bug 129802] Change wording of PDF Export File encryption and Permission dialog in Writer for clarity

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129802

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #1 from Julien Nabet  ---


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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129800] Change wording of PDF Export File encryption and Permission dialog in Writer for clarity

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129800

--- Comment #2 from Julien Nabet  ---
*** Bug 129801 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129801] Change wording of PDF Export File encryption and Permission dialog in Writer for clarity

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129801

Julien Nabet  changed:

   What|Removed |Added

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

--- Comment #1 from Julien Nabet  ---


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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129800] Change wording of PDF Export File encryption and Permission dialog in Writer for clarity

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129800

--- Comment #1 from Julien Nabet  ---
*** Bug 129802 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129803] cant download new music

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129803

Julien Nabet  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |INVALID

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 34355] Option to show track changes in margin is missing

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34355

--- Comment #103 from Dua Specialist  ---
  I will guide you right way how is Love Marriage Specialist working. 
https://duaforhusbandandwife.wordpress.com/2020/01/05/dua-for-love-marriage/

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-ux-advise] [Bug 34355] Option to show track changes in margin is missing

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=34355

--- Comment #103 from Dua Specialist  ---
  I will guide you right way how is Love Marriage Specialist working. 
https://duaforhusbandandwife.wordpress.com/2020/01/05/dua-for-love-marriage/

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise


[Libreoffice-bugs] [Bug 129803] New: cant download new music

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129803

Bug ID: 129803
   Summary: cant download new music
   Product: LibreOffice
   Version: 3.3.1 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Android Viewer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: aminmaxwel...@yandex.com

Description:
دانلود آهنگ جدید - دانلود موزیک ایرانی جدید با لینک مستقیم به همراه متن اهنگ
کیفیت اصلی 128 و 320
https://download1music.ir/
دانلود آهنگ جدید - دانلود موزیک ایرانی جدید با لینک مستقیم به همراه متن اهنگ
کیفیت اصلی 128 و 320
https://download1music.ir/
دانلود آهنگ جدید - دانلود موزیک ایرانی جدید با لینک مستقیم به همراه متن اهنگ
کیفیت اصلی 128 و 320
https://download1music.ir/

Actual Results:
دانلود آهنگ جدید - دانلود موزیک ایرانی جدید با لینک مستقیم به همراه متن اهنگ
کیفیت اصلی 128 و 320
https://download1music.ir/

Expected Results:
دانلود آهنگ جدید - دانلود موزیک ایرانی جدید با لینک مستقیم به همراه متن اهنگ
کیفیت اصلی 128 و 320
https://download1music.ir/


Reproducible: Always


User Profile Reset: No



Additional Info:
دانلود آهنگ جدید - دانلود موزیک ایرانی جدید با لینک مستقیم به همراه متن اهنگ
کیفیت اصلی 128 و 320
https://download1music.ir/

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 50916] Allow more than 1024 columns in calc

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=50916

--- Comment #137 from alenaofficial  ---
https://bestreviewsproducts.com/lightest-gaming-mouse/
Looking to alleviate carpal tunnel or repetitive strain injury without cutting
down on your computer time? Using the best ergonomic mouse should help. There
are ...

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129538] icon missing in menubar

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129538

--- Comment #1 from Xavier Van Wijmeersch  ---
in toolbar the Underline and the special icon is not showing

Version: 6.5.0.0.alpha0+
Build ID: b0a468d75ff96955e9e53027d35b248235cb68d0
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: nl-BE (en_US.UTF-8); UI-Language: en-US
Calc: threaded

and this version of LO

the bold, italic and underline icon is not showing

Version: 6.3.4.2
Build ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: nl-BE (en_US.UTF-8); UI-Language: en-US
Calc: threaded

Version: 6.4.0.0.beta1
Build ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

hope this helps

best wishes for 2020

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 120025] Many temporary files written for example gpgme-15iaRI

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120025

--- Comment #11 from xtr806...@xtra.co.nz ---
I have given up trying to use GPG and I removed all components of GnuPG, GPGME
etc. from the computer so the numerous temporary files are no longer being
created. I cannot provide any further information.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 84146] EDITING FIELDS: Variable field with format 'Standard" value not set/shown

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84146

--- Comment #8 from Chas Belov  ---
sdc.bla...@youmail.dk 

In Microsoft Excel, the General format has the description "no specific
format." If you type a number into a cell with that format, it treats it like a
number. If you type text into a cell with that format, it treats it like text.
So it is reasonable to expect that a field with the format "General" in
LibreOffice would similarly adapt to whatever I type into it. It also offers
other formats such as dates.

LibreOffice fields offer varying formats also including formats explicitly
named as being numbers and formats explicitly named as being dates.

There is nothing in the field format list that initially displays to indicate
that LibreOffice considers General to mean numeric. There is General, Text, and
several numeric options. It is only when I further click Additional formats...
that we see LibreOffice considers General to be a numeric format.

I recognize that LibreOffice is not Microsoft Office. That said, expecting
users to realize that something called "General" is a numeric format or that
the default for fields is to be a numeric format and that if you want text then
you have to explicitly choose Text and not choose General, unlike Excel, then
this is a usability issue for people who have to move between Microsoft and
LibreOffice. At the very least, you could make it obvious by changing the label
from General to General Numeric or, if you want it to be brief, Numeric.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129606] Drag-fill series produces values like 6.00000000000001

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129606

--- Comment #7 from Mike Kaganski  ---
(In reply to b. from comment #6)
> - it's likely ~0.10001 - with a dot, 

Yes, I forgot to replace my local comma with a dot (that I usually do for
convenience of others, to settle with some convention that seems to be used
more here).

> - and it's handled different in calc, both results 0.1000,
> see attached screenshot, 

And now change your example:

=0.1*60
=(1.1-1.0)*60

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 111888] change method of creating variables in Writer's "Fields" dialogue to allow creating variables without inserting

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=111888

--- Comment #10 from Mike Kaganski  ---
(In reply to sdc.blanco from comment #9)
> what is wrong with using the Type "User Field" (in Variables tab of Field
> dialog)?  This already does everything that you have described in step 3
> (of the proposed procedure) in comment 0.

It doesn't. The green checkbox is clickable, true; but it does not add a new
variable without inserting the field. At least it seems so in my testing with
Version: 6.5.0.0.alpha0+ (x64)
Build ID: adf7031e3a35fe9d43085e8b223a6e36d20a32f4
CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL:
win; 
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: CL

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129802] New: Change wording of PDF Export File encryption and Permission dialog in Writer for clarity

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129802

Bug ID: 129802
   Summary: Change wording of PDF Export File encryption and
Permission dialog in Writer for clarity
   Product: LibreOffice
   Version: 6.3.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: t...@tom.im

When you export a Writer document to PDF, you can give it two different
passwords, but the purpose of neither is as clear as it could be. Right now the
options are:

Set open password

Set permission password

As you folks know, "open" means for opening the exported PDF. "permission"
means a password on the actual .ODT document itself. Well, they're both "open"
or "permission" passwords. How about this instead?

Set password on exported PDF

Set password on Writer document

Love OpenOffice, and yes, I contribute regularly. Thanks for an awesome job,
peeps!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129801] New: Change wording of PDF Export File encryption and Permission dialog in Writer for clarity

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129801

Bug ID: 129801
   Summary: Change wording of PDF Export File encryption and
Permission dialog in Writer for clarity
   Product: LibreOffice
   Version: 6.3.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: t...@tom.im

When you export a Writer document to PDF, you can give it two different
passwords, but the purpose of neither is as clear as it could be. Right now the
options are:

Set open password

Set permission password

As you folks know, "open" means for opening the exported PDF. "permission"
means a password on the actual .ODT document itself. Well, they're both "open"
or "permission" passwords. How about this instead?

Set password on exported PDF

Set password on Writer document

Love OpenOffice, and yes, I contribute regularly. Thanks for an awesome job,
peeps!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129800] New: Change wording of PDF Export File encryption and Permission dialog in Writer for clarity

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129800

Bug ID: 129800
   Summary: Change wording of PDF Export File encryption and
Permission dialog in Writer for clarity
   Product: LibreOffice
   Version: 6.3.4.2 release
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: enhancement
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: t...@tom.im

Created attachment 156936
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156936=edit
Screen shot of the dialog in question

When you export a Writer document to PDF, you can give it two different
passwords, but the purpose of neither is as clear as it could be. Right now the
options are:

Set open password

Set permission password

As you folks know, "open" means for opening the exported PDF. "permission"
means a password on the actual .ODT document itself. Well, they're both "open"
or "permission" passwords. How about this instead?

Set password on exported PDF

Set password on Writer document

Love OpenOffice, and yes, I contribute regularly. Thanks for an awesome job,
peeps!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129799] New: Recovered document is missing a couple of paragraphs after battery depleted.

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129799

Bug ID: 129799
   Summary: Recovered document is missing a couple of paragraphs
after battery depleted.
   Product: LibreOffice
   Version: 6.0.7.3 release
  Hardware: All
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: framework
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: m...@tomaszubiri.com

Description:
Yesterday I was writing with my unplugged laptop, my OS warned me that my
battery was running out, I figured this was a good moment to end the day, so I
kept writing until the battery ran out. I expected the document to be there the
next time I started the libreoffice application.

There were 2 problems:
1- The paragraph I wrote before the battery warning was missing.
2- The paragraph I wrote after the battery warning and before shutdown were
missing.

There's 2 suggerted fixes, the first one is general and works for all cases.
The second one is a backup in case there's problems with the first one (there
shouldn't be, it's a great suggestion)

1-The frequency between autosaves should be increased so that even partial
paragraphs are saved, there's a lot of room for improvement with 2 paragraphs
missing.
2- Libreoffice should listen to battery notifications and autosave work.
Additionally it may shutdown early since it can't ensure the work will be
saved. This seems more complex to implement and less impactful than the 1st
solution though.

Steps to Reproduce:
1.Start writing document between 1 and 2 paragraphs long in about 2 minutes of
time.
2. Simulate a shutdown with the kill command.
3. Start libreoffice again.


Actual Results:
An empty document should appear.

Expected Results:
Gmail should be looked at for inspiration here, the document should be
autosaved:
- When the user stops typing for 5 seconds.
- Or after 10 seconds of consecutive typing.

That's it, pretty simple.


Reproducible: Always


User Profile Reset: No



Additional Info:
Other applications to look at would be google docs, microsoft 365 and the
desktop version.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129536] LibreOffice Viewer Android: Only listing first 12 directories

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129536

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129540] Wrong y-error bars for range cells in calc

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129540

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129537] KeyID gogLP is assigned to two strings

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129537

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129538] icon missing in menubar

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129538

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129778] FILESAVE:LibreOffice Draw can only export to pdf

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129778

QA Administrators  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129541] calc CALCULATING: autocalculate with 'shared formulas' still broken if a shared formula has #REF! problem

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129541

QA Administrators  changed:

   What|Removed |Added

 Whiteboard|| QA:needsComment

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 124792] Find function in Writer Variables

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124792

QA Administrators  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121678] Share mode won't work over samba

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121678

--- Comment #4 from QA Administrators  ---
Dear dejan.rehberger,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 125747] Calc does not compute row height properly with KDE5 vcl

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125747

--- Comment #3 from QA Administrators  ---
Dear sergio.callegari,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 102495] [META] KDE VCL backend bugs and enhancements

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=102495
Bug 102495 depends on bug 125747, which changed state.

Bug 125747 Summary: Calc does not compute row height properly with KDE5 vcl
https://bugs.documentfoundation.org/show_bug.cgi?id=125747

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129778] FILESAVE:LibreOffice Draw can only export to pdf

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129778

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 124792] Find function in Writer Variables

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=124792

--- Comment #4 from QA Administrators  ---
Dear Bruno,

Please read this message in its entirety before proceeding.

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

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

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

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

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

e) Read all comments and provide any requested information

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

a) respond via email 

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

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 125747] Calc does not compute row height properly with KDE5 vcl

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125747

QA Administrators  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 121501] writer_pdf_Export can't be used in sdk DocumentConverter.java example

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=121501

--- Comment #4 from QA Administrators  ---
Dear JS Lair,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 126252] Pasting a large amount of sheets with images is rather slow

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=126252

--- Comment #4 from QA Administrators  ---
Dear Telesto,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 115486] LibreOffice shouldn't require writable and executable memory pages at the same time

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115486

--- Comment #17 from QA Administrators  ---
Dear hessnovTHR44,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 75922] EDITING: "Correct All" (Change All) button doesnt function correctly in spelling dialog (see comment 10)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=75922

--- Comment #17 from QA Administrators  ---
Dear Peter CM,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 81003] BASIC runtime error. '380' Incorrect property value

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=81003

--- Comment #9 from QA Administrators  ---
Dear Bob,

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

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

If you have time, please do the following:

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

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

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

Please DO NOT

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


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

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


Feel free to come ask questions or to say hello in our QA chat:
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 120025] Many temporary files written for example gpgme-15iaRI

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120025

--- Comment #10 from QA Administrators  ---
Dear xtr806595,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.

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

Warm Regards,
QA Team

MassPing-NeedInfo-Ping

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] help.git: source/text

2020-01-04 Thread Seth Chaiklin (via logerrit)
 source/text/swriter/01/04090005.xhp |   30 ++
 source/text/swriter/01/04090100.xhp |2 +-
 2 files changed, 15 insertions(+), 17 deletions(-)

New commits:
commit f0321cbc4c5f8611b6d75b1312c9d198c1fad4cf
Author: Seth Chaiklin 
AuthorDate: Fri Jan 3 12:50:24 2020 +0100
Commit: Olivier Hallot 
CommitDate: Sun Jan 5 03:40:17 2020 +0100

updating help for Writer variables

- remove duplication
- aligned capitalization in help with capitalization in dialog box
- corrected labels to match dialog box
- move embedded parts to correct place in structure


Change-Id: I04cf1a2736cb3b4f4fa61fcd11cb5ee6f0f6c816
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/86171
Tested-by: Jenkins
Reviewed-by: Olivier Hallot 

diff --git a/source/text/swriter/01/04090005.xhp 
b/source/text/swriter/01/04090005.xhp
index 8c36b213a..a5a1d9dcb 100644
--- a/source/text/swriter/01/04090005.xhp
+++ b/source/text/swriter/01/04090005.xhp
@@ -64,7 +64,7 @@
 Show 
Variable
 
 
-Inserts the 
current value of the variable that you click in the Selection 
list.
+Inserts the 
current value of the variable that you click in the 
Selectlist.
 
 
 
@@ -90,7 +90,7 @@
 
 Inserts a 
new value for a variable or a User Field.
 The value 
of a variable in an Input field is only valid from where the field is inserted 
and onwards. To change the value of the variable later in the document, insert 
another Input field of the same name, but with a different value. However, the 
value of a User Field is changed globally.
-The 
variables are displayed in the Selection field. When you click the 
Insert button, the dialogInput Field appears, where you can enter 
the new value or additional text as a remark.
+The 
variables are displayed in the Select field. When you click the 
Insert button, the dialog Review 
Fields appears, where you can enter the new value or additional 
text as a remark.
 
 
 
@@ -111,7 +111,7 @@
 
 
 
-Show Page 
Variable
+Show page 
variable
 
 
 Displays 
the number of pages from the "Set page variable" reference point to this 
field.
@@ -126,28 +126,26 @@
 
 
 
-
+
+Selecton all tab pages this is called "Select", except for 
"Cross-References", which uses "Selection"
+Lists the available fields for the 
field type selected in the Type list. To insert a field, click the 
field, and then click Insert.
+To quickly insert a 
field from the Select list, hold down Command
+Ctrl and 
double-click the field.
 
 Click the format that you 
want to apply to the selected field, or click "Additional formats" to define a 
custom format.
-
-For 
user-defined fields, click the format that you want to apply in the 
Format list, or click "Additional formats" to define a custom 
format.
+Provides Format 
header and explanation
 
 Type the name of the 
user-defined field that you want to create.
-
+Provides Name header 
and explanation
 
 Enter the contents that you 
want to add to a user-defined field.
 
 
 In the Format list, 
define if the value is inserted as text or a number.
-
-Selecton "Document" and "DocInformation" tab page this is 
called "Select", on the other tab pages "Selection"
-Lists the available fields for the 
field type selected in the Type list. To insert a field, click the 
field, and then click Insert.
-To quickly insert a 
field from the list, hold down Command
-Ctrl and 
double-click the field.
+Warns that 
following types depend on the selection in the Type list
 In an HTML 
document, two additional fields are available for the "Set variable" field 
type: HTML_ON and HTML_OFF. The text that you type in the Value 
box is converted to an opening HTML tag (Value) 
or to a closing HTML (/Value) tag when the file is saved as an HTML 
document, depending on the option that you select.
-If you double-click 
an entry while holding the Ctrl key or select the desired variable and press 
the spacebar, it is immediately inserted into your document.
 Formula
-This option is 
only available if the "Insert formula" field type is selected.
+This option is 
only available if the "Insert Formula" field type is selected.
 
 
 
@@ -166,13 +164,13 @@
 
 
 Apply
-Adds the user-defined field to the 
Selection list.
+Adds the user-defined field to the 
Select list.
 
 
 
 
 Delete
-Removes the user-defined field from 
the selection list. You can only remove fields that are not used in the current 
document. To remove a field that is used in the current document from 
the list, first delete all instances of the field in the document, and then 
remove it from the list.
+Removes the user-defined field from 
the select list. You can only remove fields that are not used in the current 
document. To remove a field that is used in the current document from 
the list, first delete all instances of the field in the document, and then 
remove it from the list.
 
 
 
diff --git a/source/text/swriter/01/04090100.xhp 
b/source/text/swriter/01/04090100.xhp
index 

[Libreoffice-commits] core.git: helpcontent2

2020-01-04 Thread Seth Chaiklin (via logerrit)
 helpcontent2 |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 5fbc89478eb91d9b97f0c3d65d9946a5cec31ea3
Author: Seth Chaiklin 
AuthorDate: Sun Jan 5 03:40:17 2020 +0100
Commit: Gerrit Code Review 
CommitDate: Sun Jan 5 03:40:17 2020 +0100

Update git submodules

* Update helpcontent2 from branch 'master'
  to f0321cbc4c5f8611b6d75b1312c9d198c1fad4cf
  - updating help for Writer variables

- remove duplication
- aligned capitalization in help with capitalization in dialog box
- corrected labels to match dialog box
- move embedded parts to correct place in structure


Change-Id: I04cf1a2736cb3b4f4fa61fcd11cb5ee6f0f6c816
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/86171
Tested-by: Jenkins
Reviewed-by: Olivier Hallot 

diff --git a/helpcontent2 b/helpcontent2
index 169466b5553e..f0321cbc4c5f 16
--- a/helpcontent2
+++ b/helpcontent2
@@ -1 +1 @@
-Subproject commit 169466b5553e03aef51d91f2b1588dc48be86c4d
+Subproject commit f0321cbc4c5f8611b6d75b1312c9d198c1fad4cf
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-bugs] [Bug 129736] LibreOffice can not save document if the path content accents (Native dialog box)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129736

iantheprogram...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |WORKSFORME

--- Comment #5 from iantheprogram...@gmail.com ---
I cannot seem to replicate the bug using an almost identical file-path to what
was specified. 

Version: 6.3.4.2
Build ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa
CPU threads: 1; OS: Linux 5.0; UI render: default; VCL: gtk3; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threadedVersion: 6.3.4.2

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 120502] Assigns style to columns it cannot handle in .xlsx files

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120502

Kevin Suo  changed:

   What|Removed |Added

 Whiteboard|target:6.5.0|target:6.5.0,

--- Comment #8 from Kevin Suo  ---
Mike Kaganski: Thanks for the fix. Any plan to backport this to libreoffice-6-3
and libreoffice-6-4 branch?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


CppCheck Report Update

2020-01-04 Thread cppcheck.libreoff...@gmail.com


A new cppcheck report is available at : 
http://dev-builds.libreoffice.org/cppcheck_reports/master/


Note:
The script generating this report was run at :
2020-05-01 03:13:18 with user buildslave at host vm140 as 
/home/buildslave/source/dev-tools/cppcheck/cppcheck-report.sh -s 
/home/buildslave/source/libo-core -c /home/buildslave/source/cppcheck -w 
/home/buildslave/tmp/www

It can be found and improved here:

https://gerrit.libreoffice.org/plugins/gitiles/dev-tools/+/master/cppcheck/cppcheck-report.sh


___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


[Libreoffice-bugs] [Bug 129798] Crash in: SwViewShell::GetDoc() -- show print with a section in a footer with a hide condition

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129798

--- Comment #1 from sdc.bla...@youmail.dk ---
Another crashreport (same procedure), but running in "Normal mode": 
http://crashreport.libreoffice.org/stats/crash_details/9bcf8de9-3d1d-4749-8c6e-a4f4d2fe6f08

(which motivated the attempt in "Safe Mode")

Also crashed in:

Version: 6.5.0.0.alpha0+ (x64)
Build ID: 444f0d256957544d26b9af9a0898364e829df1b5
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; 
Locale: en-US (en_DK); UI-Language: en-US
Calc: CL

(but no URL was provided in crashreport)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129798] New: Crash in: SwViewShell::GetDoc() -- show print with a section in a footer with a hide condition

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129798

Bug ID: 129798
   Summary: Crash in: SwViewShell::GetDoc()  -- show print with a
section in a footer with a hide condition
   Product: LibreOffice
   Version: 6.3.4.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk

This bug was filed from the crash reporting server and is
br-a5387a4e-0b5e-43a4-9f16-641c2320a779.
=

Conducted in "Safe Mode"

1. Open new document.
2. Insert Footer, Insert Section (in Footer)
(show print - no problem)
3. Check Hide in Section and add a condition.
4. Create a "User Field" variable (corresponding to the variable in the
condition), and Apply.
5.  Show print
6.  Crash.

Reproducible.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129606] Drag-fill series produces values like 6.00000000000001

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129606

--- Comment #6 from b.  ---
Created attachment 156935
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156935=edit
IEEE 754 values handeled in calc

hello @Mike, 

happy new year, 

i already admitted that my comment may be valueless for you, but might be
usefule for others less experienced, 

your sample: 

1.1 - 1.0 => ~0.10009
0.1   => ~0,10001

is a little 'off' in two respects: 

- it's likely ~0.10001 - with a dot, 

- and it's handled different in calc, both results 0.1000, see
attached screenshot, 

that may result from the 'valueless placeholders' you supressed with the
valueless comment, 

thanks for correcting the citation, 

regardless of your rough tone i will be happy if you succeed in making this
little piece of calc working smooth for users without breaking functionality or
correctness ... 

reg. 

b.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129797] New: Selection Mode: Block Area. After copying and pasting, lines appeared in reversed order

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129797

Bug ID: 129797
   Summary: Selection Mode: Block Area. After copying and pasting,
lines appeared in reversed order
   Product: LibreOffice
   Version: 6.3.4.2 release
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ramiro.ar...@usa.com

Description:
This is very easy to reproduce. Select a block area. Copy the selected lines.
Paste elsewhere. Pasted lines are reversed. First appears the last line, etc. 

Steps to Reproduce:
1. Selection Mode > Block Area.
2. Select some lines
3. Copy those lines
4. Paste them elsewhere. 

Actual Results:
After pasting copied lines, these will be in reversed order. 

Expected Results:
Lines in the same order that appeared in the selected area.


Reproducible: Always


User Profile Reset: No



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129796] New: Edit Field of a Input Field Variable with a User Field variable does not give the proper Reference value

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129796

Bug ID: 129796
   Summary: Edit Field of a Input Field Variable with a User Field
variable does not give the proper Reference value
   Product: LibreOffice
   Version: 6.5.0.0.alpha0+ Master
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk

Created attachment 156934
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156934=edit
Edit Dialog boxes showing problem with Reference value

The summary indicates a symptom not the problem.

Procedure.

1. Ctrl-F2 (Variable tab)   User Field Variable (w/text format) and apply.
2. Input Field variable, with just-created User Field, insert.
3. Right-click on Inserted variable > Edit Field.

Actual result:  

1.  Slowly the edit dialog box will appear.
2.  The reference field shows diverse characters (see attachment)

Expected result:
1. Edit Dialog box quickly appears
2. Reference field should contain the string shown in the inserted variable.

Additional information.
1.  Works properly if Set Variable is used to make Variable for input box.
2.  Several times, LO froze or crashed when I tried this (as part of a regular
editing session, making different variables and inserting different input
variables -- but could not find a simple recipe to reproduce).  But the problem
with the reference field happened consistently in all cases.
3.  Does not occur with LO 6.3.4.2

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 84146] EDITING FIELDS: Variable field with format 'Standard" value not set/shown

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=84146

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 CC||sdc.bla...@youmail.dk

--- Comment #7 from sdc.bla...@youmail.dk ---
I believe this is NAB (or maybe a documentation problem).

"Standard" no longer appears as a format, but I assume it is the same as
"General" (where the same results can be obtained using LO 6.3.4.2)

General (and probably Standard) is a number format.  The procedure here is
assigning a text string to a numerical variable. So it is understandable that
Show Variable does not show anything.

If you right-click and edit field on the inserted variable and change "is" to a
number -- then that number will be shown.

If you want to show an alphabetic string, then use the Text format.  It works
as expected in LO 6.3.4.2

Given how long this bug has been here, I wonder what I have misunderstood.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 98565] FILEOPEN draw:transform="scale()" acts wrongly on line, polyline and path

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=98565

Regina Henschel  changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de
   |desktop.org |
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=98
   ||584
 Status|NEW |ASSIGNED

--- Comment #13 from Regina Henschel  ---
Not duplicate, but needs to be fixed together with bug 98584.

The error here is, that width and height of a polygon-shape is only based on
svg:width and svg:height. Additional scaling in a draw:transform attribute is
ignored.

The problem becomes visible, when import of draw:transform value skewY is fixed
(bug 98584). A vertical shearing is replaced by using a suitable rectangle,
shear it horizontal and then rotate it. This rectangle is different from the
original rectangle given by svg:width and svg:height and therefore produces an
additional scaling in the transformation matrix.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


Re: [Libreoffice-qa] Solved: Translation markers in wiki

2020-01-04 Thread Terrence Enger
On Sat, 2020-01-04 at 21:03 +0200, Ilmari Lauhakangas wrote:
> Terrence Enger kirjoitti 4.1.2020 klo 20.55:
wrote about his confusion with the mechanism supporting wiki page
translations.

> > 
> > Is this because of something I did?  What should I do?
> 
> This is some briefly transient thing. If you view the special page now, 
> you will see there are no broken pages. It probably has to do with the 
> fact that marking a page for translation creates a job in the wiki job 
> queue and we have to wait for the queue to clear to actually see the 
> final result.

Thank you, Ilmari.
Terry.


___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: https://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


Re: Duplicate .uno commands

2020-01-04 Thread Maxim Monastirsky
Hi Mike,

> So is there something I miss about these two commands behaving 
> identically?

The separate .uno:BulletsAndNumberingDialog command predates the
handling of .uno:OutlineBullet in Writer. The latter was introduced
only in 2013 as part of the sidebar feature work (commit
d02f75a8c36705924ddd6a5921fe3012fafce812, "Resolves: #i121420# merge
sidebar feature"). I believe the intent there was to have a single
command to dispatch from the sidebar's bullets/numbering popups, across
different modules, not to introduce any new behavior beyond
.uno:BulletsAndNumberingDialog.

> and is there an 
> existing mechanism to hide some .uno commands from the customization 
> UI?

Yes. Each sdi slot has 3 attributes which should be set to FALSE :
AccelConfig, MenuConfig, ToolBoxConfig. As a result, the given command
won't be reported to the customization dialog via the
XDispatchInformationProvider interface. See the actual implementation
in SfxBaseController::getConfigurableDispatchInformation and
SfxAppDispatchProvider::getConfigurableDispatchInformation.

Best regards,
Maxim

___
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice


[Libreoffice-ux-advise] [Bug 129760] an empty input field is invisible, unless the cursor happens to land on it

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129760

--- Comment #3 from sdc.bla...@youmail.dk ---
Additional information.

Ctrl-F9 does not show field codes for Input Field variables created with a Text
or User variable

Systematic procedure to see problem.

1.  Create (and insert) a variable with Text format.
2.  Create (and insert) a variable with General Format and alphabetic value 
(e.g., abcd) (I know.  But this is to illustrate a point.) 
3.  Create a User Field, with General Format and alphabetic value.
4.  Insert three input fields, one with each variable.

Actual Result:  
 - Text format variable is displayed 
 - General format variable displays (little) grey box
 - User Field (with General format) shows alphabetic value
 - Input field with Text and User displays text
 - Input field with General displays (little) grey box.

Part II.

Create and insert a User Field (with no value).
Note that a grey box is shown.

Part III.

View > Field Names (Ctrl+F9)

Actual Result:
 - Input field with Text and User variables do not show field names
 - All other fields display their contents (including the alphabetic values for
the General Format variable)

Observations.
1.  Even though the input field with a General variable and the empty User
Field does not show anything, the field itself is still shown with a grey box.
2.  Similarly, Ctrl-F9 shows the codes for the General variable Input field
box, but no field name codes are shown for the input boxes with Text and User
variables.
3.  As noted before, if you remove the contents (value) of the Text format or
User format variables, then the Input box becomes invisible, unless you move
the cursor until you "notice" that have have entered the field again. 

Retested with LO 6.3.4.2  and same results with:

Version: 6.5.0.0.alpha0+ (x64)
Build ID: 444f0d256957544d26b9af9a0898364e829df1b
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win;

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise


[Libreoffice-bugs] [Bug 129760] an empty input field is invisible, unless the cursor happens to land on it

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129760

--- Comment #3 from sdc.bla...@youmail.dk ---
Additional information.

Ctrl-F9 does not show field codes for Input Field variables created with a Text
or User variable

Systematic procedure to see problem.

1.  Create (and insert) a variable with Text format.
2.  Create (and insert) a variable with General Format and alphabetic value 
(e.g., abcd) (I know.  But this is to illustrate a point.) 
3.  Create a User Field, with General Format and alphabetic value.
4.  Insert three input fields, one with each variable.

Actual Result:  
 - Text format variable is displayed 
 - General format variable displays (little) grey box
 - User Field (with General format) shows alphabetic value
 - Input field with Text and User displays text
 - Input field with General displays (little) grey box.

Part II.

Create and insert a User Field (with no value).
Note that a grey box is shown.

Part III.

View > Field Names (Ctrl+F9)

Actual Result:
 - Input field with Text and User variables do not show field names
 - All other fields display their contents (including the alphabetic values for
the General Format variable)

Observations.
1.  Even though the input field with a General variable and the empty User
Field does not show anything, the field itself is still shown with a grey box.
2.  Similarly, Ctrl-F9 shows the codes for the General variable Input field
box, but no field name codes are shown for the input boxes with Text and User
variables.
3.  As noted before, if you remove the contents (value) of the Text format or
User format variables, then the Input box becomes invisible, unless you move
the cursor until you "notice" that have have entered the field again. 

Retested with LO 6.3.4.2  and same results with:

Version: 6.5.0.0.alpha0+ (x64)
Build ID: 444f0d256957544d26b9af9a0898364e829df1b
CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win;

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129795] PIVOTTABLE - Can't change pivot table destination (overlapping destination)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129795

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  ---
Repro
Versión: 6.3.4.2 (x64)
Id. de compilación: 60da17e045e08f1793c57c00ba83cdfce946d0aa
Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: GL; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: CL

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129736] LibreOffice can not save document if the path content accents (Native dialog box)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129736

obook  changed:

   What|Removed |Added

 Status|NEEDINFO|UNCONFIRMED
 Ever confirmed|1   |0

--- Comment #4 from obook  ---
LibreOffice can not save document if the path contains accents (Native dialog
box). For example if the path is /home/user/u...@gmail.com/Hétérogénéité
28112019/

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 120141] Templates in shellnew directory not fitting to global settings

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120141

--- Comment #7 from Nikolaus Kühn  ---
(In reply to Nikolaus Kühn from comment #6)

> This issue could be tagged with a 6.x version istead of 4.x to increase
> visibility.

Please ignore that statement, I forgot that the version tag refers to the
earliest affected

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 120141] Templates in shellnew directory not fitting to global settings

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120141

Nikolaus Kühn  changed:

   What|Removed |Added

 CC||nikolaus.ku...@gmx.de

--- Comment #6 from Nikolaus Kühn  ---
Hi, 

I have just reproduced this on my partner's new windows 10 computer (fresh
windowsn installation). 

 - Windows 10 64bit, latest version and updates
 - German (Germany) locale in the windows system

Since you asked for a more precise reproduction flow @Buovjaga: 

 * download libreoffice https://www.libreoffice.org/download/download/ (latest,
tested with 6.3.4)
 * run installer, leave all standard settings
 * start libreoffice writer from start menu
 * type "Rice  Reis"  ("reis" is german for rice)  -> "rice" underlined by
spell checker, i.e. libreoffice finds the english spellling not OK but the
german one OK.
 * close libreoffice
 * open windows explorer
 * navigate to documents folder
 * right click/tap in folder, choose "Neu -> OpenDocument Text" in context menu
("neu" is german for "new")
 * type a file name, press return
 * double click the file, opens in libreoffice
 * type "Rice Reis"  -> "Reis" underlined by spell checker, i.e. libreoffice
finds the german spelling not OK but the english one OK. 

Expected behavior in last step: "Rice" underlined in spell checker because all
defaults should be properly set to the system locale on a fresh install. 

I chose the spell checker because it's an obviously visible use case. But the
document created via the context menu in the explorer is overall not set to the
standard locale. 

---

My guess / gut feeling about the issue:
The problem is that creating a new file via the context menu in the windows
explorer is happening without any software interaction with libreoffice.
Windows solely relies on the registry information to decide what file to copy
and create. 

"Computer\HKEY_CLASSES_ROOT\.odt\LibreOffice.WriterDocument.1\ShellNew\FileName"
 contains the path to the Libreoffice installation folder and the the
libreoffice installer is not language-specific, libreoffice handles locale
defaults at first start but does not change the file in the installation folder
(which is hard because changing them requires administrator privileges). 

Maybe LO could put a file into the installation folder's
"share\template\shellnew" that is somemarked as unlocalized so it can detect
that when opening the file and set the configured locale when the file is first
opened (which would again have the downside that the file is changed and the
user would have to save even if nothing is changed).  

Not sure how other applications handle the case. 

This issue could be tagged with a 6.x version istead of 4.x to increase
visibility.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 120141] Templates in shellnew directory not fitting to global settings

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=120141

--- Comment #5 from Nikolaus Kühn  ---
Hi, 

I have just reproduced this on my partner's new windows 10 computer (fresh
windowsn installation). 

 - Windows 10, latest version and updates
 - German (Germany) locale in the windows system

Since you asked for a more precise reproduction flow @Buovjaga: 

 * download libreoffice https://www.libreoffice.org/download/download/ 
 * run installer, leave all standard settings
 * start libreoffice writer from start menu
 * type "Rice  Reis"  ("reis" is german for rice)  -> "rice" underlined by
spell checker, i.e. libreoffice finds the english spellling not OK but the
german one OK.
 * close libreoffice
 * open windows explorer
 * navigate to documents folder
 * right click/tap in folder, choose "Neu -> OpenDocument Text" in context menu
("neu" is german for "new")
 * type a file name, press return
 * double click the file, opens in libreoffice
 * type "Rice Reis"  -> "Reis" underlined by spell checker, i.e. libreoffice
finds the german spelling not OK but the english one OK. 

Expected behavior in last step: "Rice" underlined in spell checker because all
defaults should be properly set to the system locale on a fresh install. 

I chose the spell checker because it's an obviously visible use case. But the
document created via the context menu in the explorer is overall not set to the
standard locale. 

---

My guess / gut feeling about the issue:
The problem is that creating a new file via the context menu in the windows
explorer is happening without any software interaction with libreoffice.
Windows solely relies on the registry information to decide what file to copy
and create. 

"Computer\HKEY_CLASSES_ROOT\.odt\LibreOffice.WriterDocument.1\ShellNew\FileName"
 contains the path to the Libreoffice installation folder and the the
libreoffice installer is not language-specific, libreoffice handles locale
defaults at first start but does not change the file in the installation folder
(which is hard because changing them requires administrator privileges). 

Maybe LO could put a file into the installation folder's
"share\template\shellnew" that is somemarked as unlocalized so it can detect
that when opening the file and set the configured locale when the file is first
opened (which would again have the downside that the file is changed and the
user would have to save even if nothing is changed).  

Not sure how other applications handle the case.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129451] Documentation for "hide section with condition" is misleading and unnecessarily complicated

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129451

sdc.bla...@youmail.dk changed:

   What|Removed |Added

   Assignee|libreoffice-b...@lists.free |sdc.bla...@youmail.dk
   |desktop.org |

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 111888] change method of creating variables in Writer's "Fields" dialogue to allow creating variables without inserting

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=111888

--- Comment #9 from sdc.bla...@youmail.dk ---
(In reply to Roman Kuznetsov from comment #6)
> because this is enhancement

If you are using the variable globally, then what is wrong with using the Type
"User Field" (in Variables tab of Field dialog)?  This already does everything
that you have described in step 3 (of the proposed procedure) in comment 0.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129795] New: PIVOTTABLE - Can't change pivot table destination (overlapping destination)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129795

Bug ID: 129795
   Summary: PIVOTTABLE - Can't change pivot table destination
(overlapping destination)
   Product: LibreOffice
   Version: 6.3.3.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Calc
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: jwmp5...@gmail.com

Description:
Related to Bug 89308 - PIVOTTABLE: Can't update pivot table destination

Using LibreOffice Calc Version@ 6.3.3.2 (x64)
OS: Windows 10

This issue does not move the pivot table if it overlaps the previous copy (i.e.
cannot create a copy on top of the existing table). Nor can you move it by
inserting columns or rows beside or above the table.
If you do move the pivot table to a non-overlapping region, then the associated
graph is deleted.



Steps to Reproduce:
Create a pivot table and associated graph of the data.

1. Attempt to move the pivot table by inserting a column to the left (or row
above). Pivot table moves correctly on the spreadsheet (but destination is not
updated in the properties).
2. Refresh the table. Pivot table reverts to the original location.
3. Use Properties -> Source and Destination -> Selection to manually alter the
column (or row) by one letter. Click OK. Pivot Table does not move, Destination
remains the same.
4. Try the same by selecting the desired location with the mouse. Pivot Table
does not move.
5. Change the destination to a non-overlapping location. The associated graph
is deleted (following a confirmation prompt).



Actual Results:
Pivot table does not move

Expected Results:
Table reverts / remains in original location


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
I understand that moving the table is currently a copy/delete procedure and may
not be easily fixed. I just wanted to highlight the issue in case someone had a
bright idea.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129794] New: UI shows wrong values of elements size (width/height) when the 'millimeter' measure is chosen

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129794

Bug ID: 129794
   Summary: UI shows wrong values of elements size (width/height)
when the 'millimeter' measure is chosen
   Product: LibreOffice
   Version: 6.2.8.2 release
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Draw
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: ceene...@yahoo.es

Description:
The 'element properties' shown at the right of the screen has a section
'Position and size' where this data is shown. If the application properties are
set to use 'millimeter' as default measurement, then the position is shown
correctly but the size doesn't: the size is shown in inches values despite
after the numeric value the 'mm' literal is shown. Example: if the object has a
size of 254x127mm then the size shown is '10,00 mm' and '5,00 mm'.

If the properties dialog is opened, then the size is shown correctly in the
dialog, and if the values are changed then the UI is refreshed accordingly. But
if another object is then selected, then the UI reverts back to showing the
values in the wrong way again

Steps to Reproduce:
1. Set the application preferences to use millimeters as the default metric
2. Create a new drawing and create an object of any size


Actual Results:
The size shown in the UI is expressed in inches (despite the 'mm' literal is
shown after the numeric value)

Expected Results:
The size shown in the UI should be expresed in millimeters


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Versión: 6.2.8.2 (x64)
Id. de compilación: f82ddfca21ebc1e222a662a32b25c0c9d20169ee
Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: predet.; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129778] FILESAVE:LibreOffice Draw can only export to pdf

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129778

--- Comment #5 from VincentYu  ---
cleaned user profile(reset to factory), it's still the same. Since this is
already the EOL build, it's supposed to be the most mature/stable one. I don't
have confidence on newer versions until it reaches at least x.x.5.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 87525] Make 'Current selection only' in Find and Replace detect range selections that happen after the dialog is opened

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=87525

Buovjaga  changed:

   What|Removed |Added

Summary|Remove the option 'Current  |Make 'Current selection
   |selection only' in Find and |only' in Find and Replace
   |Replace |detect range selections
   ||that happen after the
   ||dialog is opened

--- Comment #19 from Buovjaga  ---
(In reply to Michael Bauer from comment #18)
> > Michael, please edit the misleading title.
> You can't edit bug titles.

You can, though. I did it.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129543] UI: strikethrough command has keyboard equivalent but what?

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129543

Nick Levinson  changed:

   What|Removed |Added

 Resolution|INSUFFICIENTDATA|NOTABUG

--- Comment #8 from Nick Levinson  ---
Yes, that's it. Since I was typing randomly including in the numerals keyboard
row, I probably typed two separate hyphens then didn't expect to see them in
the output (and didn't see them) and so they got swallowed up by AutoCorrect
and strikethrough appeared. I don't usually type randomly but I changed
AutoCorrect settings anyway. I'll change the status again. Thank you very much.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 104627] FILEOPEN: very slow-loading of .docx file

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104627

--- Comment #11 from Buovjaga  ---
Retested, used a stopwatch and I got 2min 33s, so the same as in 2016 with the
same computer.

Arch Linux 64-bit
Version: 6.5.0.0.alpha0+
Build ID: 2dfc1dce87a0509e76d3d5875e03e3fae5d677d7
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 21 December 2019

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 117684] soffice.bin uses 100% CPU -- resolves when 'saving' document

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=117684

Buovjaga  changed:

   What|Removed |Added

 Status|REOPENED|NEW

--- Comment #13 from Buovjaga  ---
Setting this to NEW, so it does not go away

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129792] Horizontal line glitches in Writer

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129792

--- Comment #2 from mvarne...@yahoo.com ---
Version: 6.2.8.2
Build ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee
CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; 
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129793] Does the "Field codes" option in the Writer options "View" dialog have any purpose?

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129793

sdc.bla...@youmail.dk changed:

   What|Removed |Added

Summary|Does the "Field codes"  |Does the "Field codes"
   |option in Writer View have  |option in the Writer
   |any purpose?|options "View" dialog have
   ||any purpose?
   Keywords||needsUXEval

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129792] Horizontal line glitches in Writer

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129792

--- Comment #1 from mvarne...@yahoo.com ---
Created attachment 156933
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156933=edit
Screenshot of Glitch

This shot seems to show the line being stretched with artifacts. The issue also
often manifests as shortening, i.e., part of a line missing.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129793] New: Does the "Field codes" option in Writer View have any purpose?

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129793

Bug ID: 129793
   Summary: Does the "Field codes" option in Writer View have any
purpose?
   Product: LibreOffice
   Version: 6.3.4.2 release
  Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: sdc.bla...@youmail.dk

In the spirit of simplification.  

Maybe the "Field Codes" option can be removed from:

Tools > Options > LO Writer > View - Field Codes

It does not seem to provide or do anything that View > Field Codes (Ctrl-F9)
already provide.  

If true, then a rare opportunity to simply a UI dialog box.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129543] UI: strikethrough command has keyboard equivalent but what?

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129543

Maxim Monastirsky  changed:

   What|Removed |Added

 CC||momonas...@gmail.com

--- Comment #7 from Maxim Monastirsky  ---
Maybe it happened because of AutoCorrect? In which case you can disable it via
Tools > AutoCorrect > AutoCorrect Options... > Options tab > Automatic *bold*,
/italic/, -strikeout- and _underline_.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129792] New: Horizontal line glitches in Writer

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129792

Bug ID: 129792
   Summary: Horizontal line glitches in Writer
   Product: LibreOffice
   Version: 6.2.8.2 release
  Hardware: x86-64 (AMD64)
OS: Mac OS X (All)
Status: UNCONFIRMED
  Severity: minor
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: mvarne...@yahoo.com

Description:
In both new and existing Writer documents, I am getting horizontal glitches
that go all the way across the page. Usually it appears one or more pixel lines
are missing from the text. Occasionally there will be a one-pixel line of
gibberish by itself. It is usually necessary to scroll past the glitch, or
reformat the line, to get it to return to normal. I don't recall seeing this in
previous versions (I recently upgraded from perhaps 6.2.3). It's not easy to
reproduce, but does happen pretty frequently (several times in half hour of
editing).

Steps to Reproduce:
1.Scroll and edit randomly.
2.Seems to occur more often with shorter fonts such as Times New Roman 12 and
with mixed line spacing, but this might be random chance.

Actual Results:
Glitch eventually appears.

Expected Results:
No glitch.


Reproducible: Sometimes


User Profile Reset: Yes



Additional Info:

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129787] Offline help installed but not being accessed

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129787

t...@tim-passingham.co.uk changed:

   What|Removed |Added

 Resolution|--- |NOTABUG
 CC||t...@tim-passingham.co.uk
 Status|UNCONFIRMED |RESOLVED

--- Comment #1 from t...@tim-passingham.co.uk ---
Apologies. My mistake.  

I had forgotten that the (good old) help system with a usable contents list and
index has been downgraded to a (not very good or usable) browser system based
on albeit using local files.

NotABug

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 127190] FILESAVE: math crashes when export to pdf (steps: comment 8, not always reproducible)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=127190

--- Comment #24 from MM  ---
Unconfirmed on windows 10 x64 with Version: 6.3.4.2 (x64)
Build ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa
CPU threads: 12; OS: Windows 10.0; UI render: default; VCL: win

Unconfirmed on mint 19.3 x64 with Version: 6.5.0.0.alpha0+
Build ID: f6cf80c81043d84606a5b5f7d93ae958307a16d3
CPU threads: 5; OS: Linux 5.0; UI render: default; VCL: gtk3; 
TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time:
2019-12-22_08:24:32
Locale: en-US (en_US.UTF-8); UI-Language: en-US
Calc: threaded

So it seems fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] dev-tools.git: help3/xhpeditor

2020-01-04 Thread Olivier Hallot (via logerrit)
 help3/xhpeditor/buttons.php |3 ++-
 help3/xhpeditor/index.php   |8 
 help3/xhpeditor/snippets.js |   29 -
 3 files changed, 22 insertions(+), 18 deletions(-)

New commits:
commit 08ee150ead33a9fd8fd6e8308420a2d05eb3e9f3
Author: Olivier Hallot 
AuthorDate: Sat Jan 4 15:07:15 2020 -0300
Commit: Olivier Hallot 
CommitDate: Sat Jan 4 21:03:57 2020 +0100

xhpeditor: fixes and improvements

- close bracket at right place
- improve icontable snippet
- add image paragraph
- better switch layout
- better switchinline layout

Change-Id: Ib1f57d0ba35937a5b81427d180d0c5a53769ecaa
Reviewed-on: https://gerrit.libreoffice.org/c/dev-tools/+/86228
Reviewed-by: Olivier Hallot 
Tested-by: Olivier Hallot 

diff --git a/help3/xhpeditor/buttons.php b/help3/xhpeditor/buttons.php
index 80efa3c..27dd890 100644
--- a/help3/xhpeditor/buttons.php
+++ b/help3/xhpeditor/buttons.php
@@ -27,7 +27,7 @@ echo '
 
 Tables:
 Table Full
-TableRow
+Table Row
 Table Cell
 Icon Table
 
@@ -38,6 +38,7 @@ echo '
 tip
 bascode-par
 pycode-par
+image-par
 
 Characters:
 emph
diff --git a/help3/xhpeditor/index.php b/help3/xhpeditor/index.php
index b732314..e01a172 100644
--- a/help3/xhpeditor/index.php
+++ b/help3/xhpeditor/index.php
@@ -109,22 +109,22 @@ $xhp = $_POST["xhpdoc"];
 foreach ($xmlarray->xpath("//$tag_uniq") as $tag){
 $idarray[$i] = $tag['id'];
 ++$i;
+}
 }
 $dupped_array =  
array_values(array_unique(array_diff_key($idarray, array_unique($idarray;
 if (count($dupped_array) > 0){
 echo 'Found duplicated ids:';
 foreach($dupped_array as $dup) {
-echo "$dup";
+echo "$dup";
 }
 }else{
 echo "No duplicates ids found.";
 }
-}
 }elseif (isset($_POST["get_patch"])) {
 echo 'Get Patch:';
 } else {
-echo 'Boo:';
-echo 'Aha!';}
+echo 'Viewing Area';
+}
 ?>
 
 
diff --git a/help3/xhpeditor/snippets.js b/help3/xhpeditor/snippets.js
index 3c5c18d..bab3b1b 100644
--- a/help3/xhpeditor/snippets.js
+++ b/help3/xhpeditor/snippets.js
@@ -67,19 +67,22 @@ function pycode_par() {
 editor.replaceSelection(a1 + editor.doc.getSelection() + a2,'');
 }
 
+function image_par() {
+var a1 = '';
+var a2 = '\n';
+editor.replaceSelection(a1 + editor.doc.getSelection() + a2,'');
+}
 // Tables
 // simple table cell
 function tCell (role){
 return '   \n   \n   \n';
 }
 
-
 function iconTable() {
 var a1 = '\n\n
\n';
-var a2 = '\n
';
-var a3 = 'CHANGE ME\n\n
\n' + tCell();
-var a4 = '\n\n\n';
-editor.replaceRange(a1 + a2 + a3 + a4, editor.doc.getCursor());
+var a2 = '\nIcon\n';
+var a3 = '\n   \n' + tCell("paragraph") + '
\n\n';
+editor.replaceRange(a1 + a2 + a3, editor.doc.getCursor());
 }
 
 function tableCell() {
@@ -171,19 +174,19 @@ function _widget() {
 // switches
 
 function switchXHP(type) {
+var type_string = (type=='sys') ? "MAC | UNIX | WIN" : "WRITER | CALC | 
IMPRESS | DRAW | BASE | MATH";
 var a1 = '\n';
-var a2 = 'CHANGE ME\n';
-var a3 = 'DEFAULT STUFF\n';
-var a4 = '\n';
-editor.replaceRange(a1 + a2 + a3 + a4, editor.doc.getCursor());
+var a2 = '\nCHANGE ME\n\n';
+var a3 = '\nDEFAULT STUFF\n\n\n';
+editor.replaceRange(a1 + a2 + a3, editor.doc.getCursor());
 }
 
 function switchInline(type) {
+var type_string = (type=='sys') ? "MAC | UNIX | WIN" : "WRITER | CALC | 
IMPRESS | DRAW | BASE | MATH";
 var a1 = '';
-var a2 = 'CHANGE 
ME';
-var a3 = 'DEFAULT STUFF';
-var a4 = '';
-editor.replaceRange(a1 + a2 + a3 + a4, editor.doc.getCursor());
+var a2 = 'CHANGE ME';
+var a3 = 'DEFAULT STUFF';
+editor.replaceRange(a1 + a2 + a3, editor.doc.getCursor());
 }
 function MenuPrefMAC(){
 editor.replaceRange('%PRODUCTNAME - 
PreferencesTools - 
Options -  ', 
editor.doc.getCursor());
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-bugs] [Bug 108037] CRASH: Huge memory usage (2.800 MB in 64-bit), additionally crash (on 1.400 MB in 32-bit) when exporting 58-pages ODP to PDF

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108037

--- Comment #12 from Xavier Van Wijmeersch  ---
I have 4.852 MB memory at the end of export with fresh build master

Version: 6.5.0.0.alpha0+
Build ID: b0a468d75ff96955e9e53027d35b248235cb68d0
CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3; 
Locale: nl-BE (en_US.UTF-8); UI-Language: en-US
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129673] EDITING: spell-check dictionary expansion

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129673

--- Comment #2 from Nick Levinson  ---
I didn't see an extension when I searched all categories for genitive,
possessive, apostrophe, uncommon, rare, or law and medicine got only a Finnish
dictionary and grammar checker.

But I'm not clear if an extension could be designed to interact with another to
produce a result not listed in either one, or to interact with a default or
default-loadable dictionary. So, the preloaded English dictionaries would need
modification to handle the straight/curved apostrophe and, if that's not done
by adding entries (like shoe, shoe's, shoes', and curved equivalents) the part
of LO or Writer that applies dictionaries might need a patch to interpret a
dictionary for this functionality (like shoe[apostrophe-code]s and
shoes[apostrophe-code] in the dictionary, perhaps where embedded are some
Unicoode 4-byte characters not used in a natural language).

Making an easier way for loading dictionaries and dictionary features would be
good for nongeeks but I suspect will be objected to as redundant of the
existing method for loading all kinds of extensions. Nongeeks won't think of
French as an extension, so a button in the F7 Spelling dialog would increase
LO's usefulness to nongeeks.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129543] UI: strikethrough command has keyboard equivalent but what?

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129543

Nick Levinson  changed:

   What|Removed |Added

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

--- Comment #6 from Nick Levinson  ---
Because it's virtually irreproducible and in my experience rare and comments
say it hasn't been found in the places where it should be, I'm closing this as
an unsolvable mystery. Thanks anyway.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 62594] writer: invisible input field for defined variable is not possible

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=62594

sdc.bla...@youmail.dk changed:

   What|Removed |Added

 CC||sdc.bla...@youmail.dk
 Status|NEW |NEEDINFO

--- Comment #3 from sdc.bla...@youmail.dk ---
(In reply to Pit Zaclade from comment #0)
> 
> Therefore it is not possible to put any instructions for this variable so
> that the user can fill in the variable with suitable terms.

According to help, it is not possible to make input fields invisible.

https://help.libreoffice.org/latest/en-US/text/swriter/01/04090005.html#hd_id3150891

If the actual problem for you is to put instructions into an input field, then
you do not need to make it invisible. You can enter instructions in the input
field.

If that is not what you wanted, then please explain again.  I will change
status to NEEDINFO


(In reply to Alexandre Falcão from comment #2)

> All the steps are reported this file.

Thanks for the detailed report. Your procedure is correct.  But I could not
reproduce the problem using LO 6.3.4.2

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 104956] Firebird: Tabledesign - VARCHAR counts wrong with special characters

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=104956

Buovjaga  changed:

   What|Removed |Added

 Status|REOPENED|NEW

--- Comment #4 from Buovjaga  ---
Let's put back to NEW, then as no one attempted to tackle this specific report.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


Re: [Libreoffice-qa] Translation markers in wiki

2020-01-04 Thread Ilmari Lauhakangas

Terrence Enger kirjoitti 4.1.2020 klo 20.55:

The page I changed is QA/Bibisect.

After I mark the page for translation, the source for the page has
newly added "" above the paragraph I added.

However, the system displays page "Page translation"
;.  At the
bottom of the page, it tells me:

 Broken pages

 An old version of this page is marked for translation, but the
 latest version cannot be marked for translation.

   1. QA/Bibisect (remove from translation)

Is this because of something I did?  What should I do?


This is some briefly transient thing. If you view the special page now, 
you will see there are no broken pages. It probably has to do with the 
fact that marking a page for translation creates a job in the wiki job 
queue and we have to wait for the queue to clear to actually see the 
final result.


Ilmari
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: https://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


[Libreoffice-bugs] [Bug 129742] Libreoffice Crash on startup in Arch Linux

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129742

Victor  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |NOTABUG

--- Comment #6 from Victor  ---
Hey Roman, I resolved the issue. It looks like there was something borked
specific to my system.

I ran a pacman command to reinstall every package on my system:

```sudo pacman -Qqn | sudo pacman -S -```

After running this & rebooting, libreoffice works now!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


Re: [Libreoffice-qa] Translation markers in wiki

2020-01-04 Thread Terrence Enger
On Sat, 2020-01-04 at 16:59 +0200, Ilmari Lauhakangas wrote:
> Terrence Enger kirjoitti 2.1.2020 klo
23.53:

asking about translation markers in wiki pages.

> We are now using the standard translation system that is also used in 
> Wikipedia. Our own summarised instructions for using it are here: 
> https://wiki.documentfoundation.org/TDF_Wiki/Multilingual#Content_with_global_focus
> 
> The markers are added automatically. They should not be copied manually.
> 
> I quote from the article:
> "When you add or change content in the source page, this will appear at 
> the top of the page: This page has changes since it was last marked for 
> translation. Click the link "marked for translation" to bring the 
> translation system up to date following the same process as in the 
> initial marking for translation."

The page I changed is QA/Bibisect.

After I mark the page for translation, the source for the page has
newly added "" above the paragraph I added.

However, the system displays page "Page translation"
;.  At the
bottom of the page, it tells me:

Broken pages

An old version of this page is marked for translation, but the
latest version cannot be marked for translation.

  1. QA/Bibisect (remove from translation)

Is this because of something I did?  What should I do?

Thank you,
Terry.

___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: https://lists.freedesktop.org/mailman/listinfo/libreoffice-qa
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://lists.freedesktop.org/archives/libreoffice-qa/


[Libreoffice-bugs] [Bug 129742] Libreoffice Crash on startup in Arch Linux

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129742

--- Comment #5 from Victor  ---
It made it much further this time, but it failed at this step:

make[4]: Leaving directory
'/home/victor/Downloads/libreoffice-6.3.4.2/workdir/UnpackedTarball/openssl/crypto/evp'
making all in crypto/asn1...
make[4]: Entering directory
'/home/victor/Downloads/libreoffice-6.3.4.2/workdir/UnpackedTarball/openssl/crypto/asn1'
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_object.o
a_object.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_bitstr.o
a_bitstr.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_utctm.o
a_utctm.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_gentm.o
a_gentm.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_time.o
a_time.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_int.o
a_int.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_octet.o
a_octet.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_print.o
a_print.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_type.o
a_type.c
gcc -fPIC  -fvisibility=hidden -I.. -I../.. -I../modes -I../asn1 -I../evp
-I../../include  -DOPENSSL_THREADS -D_REENTRANT -O3 -Wall   -c -o a_set.o
a_set.c
a_set.c:74:12: internal compiler error: Segmentation fault
   74 | static int SetBlobCmp(const void *elem1, const void *elem2)
  |^~
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
make[4]: *** [: a_set.o] Error 1
make[4]: Leaving directory
'/home/victor/Downloads/libreoffice-6.3.4.2/workdir/UnpackedTarball/openssl/crypto/asn1'
make[3]: *** [Makefile:90: subdirs] Error 1
make[3]: Leaving directory
'/home/victor/Downloads/libreoffice-6.3.4.2/workdir/UnpackedTarball/openssl/crypto'
make[2]: *** [Makefile:287: build_crypto] Error 1
make[2]: Leaving directory
'/home/victor/Downloads/libreoffice-6.3.4.2/workdir/UnpackedTarball/openssl'
make[1]: ***
[/home/victor/Downloads/libreoffice-6.3.4.2/external/openssl/ExternalProject_openssl.mk:71:
/home/victor/Downloads/libreoffice-6.3.4.2/workdir/ExternalProject/openssl/build]
Error 1
make: *** [Makefile:282: build] Error 2

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-commits] core.git: vcl/commonfuzzer.mk

2020-01-04 Thread Caolán McNamara (via logerrit)
 vcl/commonfuzzer.mk |2 ++
 1 file changed, 2 insertions(+)

New commits:
commit 0b00112e112f80f9342f39e4d338d5a89e522ab9
Author: Caolán McNamara 
AuthorDate: Sat Jan 4 16:08:45 2020 +
Commit: Caolán McNamara 
CommitDate: Sat Jan 4 19:03:56 2020 +0100

ofz#19766 fix Build-Failure

Change-Id: I4df1dec271980a8a9eab9c2ee2c687ef938082d5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86225
Reviewed-by: Caolán McNamara 
Tested-by: Caolán McNamara 

diff --git a/vcl/commonfuzzer.mk b/vcl/commonfuzzer.mk
index f0366d7e2179..b58a5bb5eccc 100644
--- a/vcl/commonfuzzer.mk
+++ b/vcl/commonfuzzer.mk
@@ -45,10 +45,12 @@ fuzzer_core_libraries = \
 basctl \
 avmedia \
 basegfx \
+bib \
 canvastools \
 configmgr \
 cppcanvas \
 ctl \
+dba \
 dbtools \
 deployment \
 deploymentmisc \
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-commits] core.git: sc/inc sc/source

2020-01-04 Thread Caolán McNamara (via logerrit)
 sc/inc/externalrefmgr.hxx|6 +++---
 sc/source/ui/docshell/externalrefmgr.cxx |4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

New commits:
commit 06de11f1d419f04a827bc6d6bc323f1c87ad83a5
Author: Caolán McNamara 
AuthorDate: Sat Jan 4 14:41:25 2020 +
Commit: Caolán McNamara 
CommitDate: Sat Jan 4 18:36:49 2020 +0100

ofz#19796 Indirect-leak

Change-Id: I144a1dd7901c90a979a018576404b84ece36a79b
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86222
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 
Tested-by: Caolán McNamara 

diff --git a/sc/inc/externalrefmgr.hxx b/sc/inc/externalrefmgr.hxx
index b0b81ea705e8..b95d6d1a0fd1 100644
--- a/sc/inc/externalrefmgr.hxx
+++ b/sc/inc/externalrefmgr.hxx
@@ -21,6 +21,7 @@
 #define INCLUDED_SC_INC_EXTERNALREFMGR_HXX
 
 #include "address.hxx"
+#include "document.hxx"
 #include 
 #include 
 #include 
@@ -40,7 +41,6 @@
 #include 
 #include 
 
-class ScDocument;
 class ScTokenArray;
 namespace weld { class Window; }
 
@@ -299,7 +299,7 @@ public:
 void clearCacheTables(sal_uInt16 nFileId);
 
 // Get the fake doc used to pass to methods that need an ScDocument in 
order to do row/col validation
-const ScDocument* getFakeDoc() const { return mpFakeDoc; }
+const ScDocument* getFakeDoc() const { return mxFakeDoc.get(); }
 
 private:
 struct RangeHash
@@ -358,7 +358,7 @@ private:
 private:
 mutable osl::Mutex maMtxDocs;
 mutable DocDataType maDocs;
-ScDocument* mpFakeDoc; // just to have something to pass to the methods 
that need to validate columns/rows
+ScDocumentUniquePtr mxFakeDoc; // just to have something to pass to the 
methods that need to validate columns/rows
 };
 
 class SC_DLLPUBLIC ScExternalRefManager final : public 
formula::ExternalReferenceHelper, public SfxListener
diff --git a/sc/source/ui/docshell/externalrefmgr.cxx 
b/sc/source/ui/docshell/externalrefmgr.cxx
index 56273f1b6c99..c164c548424e 100644
--- a/sc/source/ui/docshell/externalrefmgr.cxx
+++ b/sc/source/ui/docshell/externalrefmgr.cxx
@@ -457,7 +457,7 @@ ScExternalRefCache::CellFormat::CellFormat() :
 }
 
 ScExternalRefCache::ScExternalRefCache()
- : mpFakeDoc(new ScDocument())
+ : mxFakeDoc(new ScDocument())
 {}
 
 ScExternalRefCache::~ScExternalRefCache() {}
@@ -687,7 +687,7 @@ ScExternalRefCache::TokenArrayRef 
ScExternalRefCache::getCellRangeData(
 
 ScMatrixToken aToken(xMat);
 if (!pArray)
-pArray.reset(new ScTokenArray(mpFakeDoc));
+pArray.reset(new ScTokenArray(mxFakeDoc.get()));
 pArray->AddToken(aToken);
 
 bFirstTab = false;
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-commits] core.git: Makefile.in

2020-01-04 Thread Caolán McNamara (via logerrit)
 Makefile.in |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit 6fbfb54086c10f0107dc7026eaeffd177eda56c3
Author: Caolán McNamara 
AuthorDate: Sat Jan 4 14:52:40 2020 +
Commit: Caolán McNamara 
CommitDate: Sat Jan 4 18:35:26 2020 +0100

allow root under podman

Change-Id: I66dc674aab8dc86c95495754400c5e64b2583599
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/86223
Tested-by: Jenkins
Reviewed-by: Caolán McNamara 
Tested-by: Caolán McNamara 

diff --git a/Makefile.in b/Makefile.in
index 50b995df7499..9d362ef1b4d0 100644
--- a/Makefile.in
+++ b/Makefile.in
@@ -60,7 +60,7 @@ else # MAKE_RESTARTS
 all: build
 
 check-if-root:
-   @if test ! `uname` = 'Haiku' -a `id -u` = 0 && ! grep -q 'lxc\|docker' 
/proc/self/cgroup; then \
+   @if test ! `uname` = 'Haiku' -a `id -u` = 0 && ! grep -q 'lxc\|docker' 
/proc/self/cgroup && ! grep -q 'libpod_parent' /proc/self/cgroup; then \
echo; \
echo 'Building LibreOffice as root is a very bad idea, use a 
regular user.'; \
echo; \
___
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits


[Libreoffice-bugs] [Bug 72080] CONFIGURATION: Set default Find (Ctrl+F) options, either separate, or based on settings in find dialog (Ctrl+H)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72080

V Stuart Foote  changed:

   What|Removed |Added

   Keywords||needsUXEval
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=62
   ||601
 CC||heiko.tietze@documentfounda
   ||tion.org,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||mikekagan...@hotmail.com,
   ||vstuart.fo...@utsa.edu
 Whiteboard|BSA |

--- Comment #2 from V Stuart Foote  ---
@Heiko, *

The "fix" for bug 62601 did not fully segregate the Find bar +F from the
Find & Replace dialog +H; leaving lingering issues like bug 115665

Some suggestions to merge configuration/GUI like bug 129783, and many one-off
requests to add settings to the Find bar (bound to or independent) from the
Find & Replace dialog settings continue to arrive.

Seems this needs a UX-Advise discussion of how to proceed, so we can handle UX
requests and design in a consistent fashion.  

Should the Find bar offer customization for the search functions of the Find &
Replace dialog?  Should it be a limited set of search functions?  Should the
configuration of the Find bar fully pick up its settings from the Find &
Replace dialog--and be stateful/recorded to user profile?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-ux-advise] [Bug 72080] CONFIGURATION: Set default Find (Ctrl+F) options, either separate, or based on settings in find dialog (Ctrl+H)

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=72080

V Stuart Foote  changed:

   What|Removed |Added

   Keywords||needsUXEval
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=62
   ||601
 CC||heiko.tietze@documentfounda
   ||tion.org,
   ||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||mikekagan...@hotmail.com,
   ||vstuart.fo...@utsa.edu
 Whiteboard|BSA |

--- Comment #2 from V Stuart Foote  ---
@Heiko, *

The "fix" for bug 62601 did not fully segregate the Find bar +F from the
Find & Replace dialog +H; leaving lingering issues like bug 115665

Some suggestions to merge configuration/GUI like bug 129783, and many one-off
requests to add settings to the Find bar (bound to or independent) from the
Find & Replace dialog settings continue to arrive.

Seems this needs a UX-Advise discussion of how to proceed, so we can handle UX
requests and design in a consistent fashion.  

Should the Find bar offer customization for the search functions of the Find &
Replace dialog?  Should it be a limited set of search functions?  Should the
configuration of the Find bar fully pick up its settings from the Find &
Replace dialog--and be stateful/recorded to user profile?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise


[Libreoffice-bugs] [Bug 62601] Quick search (ctrl+f) affected by invisible option from the search-and-replace dialog

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=62601

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129742] Libreoffice Crash on startup in Arch Linux

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129742

--- Comment #4 from Roman Kuznetsov <79045_79...@mail.ru> ---
(In reply to Victor from comment #3)
> Hey Roman, thanks for the reply, I attempted to run autogen, but it halts at
> this error:
> 
> checking if jdk.net.URLClassPath.ClassPathURLCheck is disabled... configure:
> error: no - Java unit tests will break!
> 
> Not really sure how to proceed from here.

Try

./autogen.sh --without-java

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129742] Libreoffice Crash on startup in Arch Linux

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129742

--- Comment #3 from Victor  ---
Hey Roman, thanks for the reply, I attempted to run autogen, but it halts at
this error:

checking if jdk.net.URLClassPath.ClassPathURLCheck is disabled... configure:
error: no - Java unit tests will break!

Not really sure how to proceed from here.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-ux-advise] [Bug 129781] [UI] make "find in current selection" as default behavior

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129781

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Libreoffice-ux-advise mailing list
Libreoffice-ux-advise@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-ux-advise


[Libreoffice-bugs] [Bug 125282] UX: The Find bar should search in “Current selection only” if a cell range is selected

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=125282

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129781] [UI] make "find in current selection" as default behavior

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129781

V Stuart Foote  changed:

   What|Removed |Added

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

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129791] vertical text is clipped in display - pdf export and print are ok

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129791

--- Comment #1 from joe...@joehtg.co.at ---
Created attachment 156932
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156932=edit
Screenshot of display in Writer - parts of the text are missing

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 129791] New: vertical text is clipped in display - pdf export and print are ok

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=129791

Bug ID: 129791
   Summary: vertical text is clipped in display - pdf export and
print are ok
   Product: LibreOffice
   Version: 6.4.0.1 rc
  Hardware: x86-64 (AMD64)
OS: Windows (All)
Status: UNCONFIRMED
  Severity: normal
  Priority: medium
 Component: Writer
  Assignee: libreoffice-bugs@lists.freedesktop.org
  Reporter: joe...@joehtg.co.at

Created attachment 156931
  --> https://bugs.documentfoundation.org/attachment.cgi?id=156931=edit
Word file containing vertical text "oktober 2018"

Attachment VertikalText.docx displays correctly in Word (Office 365).
Display in LibreOffice Writer is clipped, last digit 8 is not displayed at all.
Display is also garbled when editing or rewriting the text "oktober 2018".

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 108743] [META] Find toolbar bugs and enhancements

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=108743

V Stuart Foote  changed:

   What|Removed |Added

 Depends on||115665


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=115665
[Bug 115665] Format in the CTRL+H search affects the CTRL+F search
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


[Libreoffice-bugs] [Bug 115665] Format in the CTRL+H search affects the CTRL+F search

2020-01-04 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=115665

V Stuart Foote  changed:

   What|Removed |Added

 CC||vstuart.fo...@utsa.edu
 Blocks||108743


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=108743
[Bug 108743] [META] Find toolbar bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.___
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs


  1   2   >