[Libreoffice-bugs] [Bug 155308] New: Dialog Record Search in Base forms: Wrong activated button "Help" instead of "Search"
https://bugs.documentfoundation.org/show_bug.cgi?id=155308 Bug ID: 155308 Summary: Dialog Record Search in Base forms: Wrong activated button "Help" instead of "Search" Product: LibreOffice Version: 7.6.0.0 alpha0+ Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@familiegrosskopf.de Created attachment 187285 --> https://bugs.documentfoundation.org/attachment.cgi?id=187285=edit Open the attached database, open the form and try search dialog Open the attached Base file. Open the form. Start "Find Record" (left on navigation bar). Dialog "Record Search" will appear. Button "Search" will be disabled, because there is no entry for searching. Type 'j' as Search for → Text Button "Search" will be enabled and activated. Press Enter. First result is found. Now button "Help" is activated. "Search" should be activated here. You won't need "Help" while you have started searching. You want to get next result, not a (wrong) link to LibreOffice help. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154910] Converting a pdf from A3 word file with page breaks using libre office overlaps the pages and makes it hard to read
https://bugs.documentfoundation.org/show_bug.cgi?id=154910 --- Comment #4 from shridhar.sanje...@scania.com --- Created attachment 187284 --> https://bugs.documentfoundation.org/attachment.cgi?id=187284=edit attached pdf created as output -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113209] [META] UI bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113209 BogdanB changed: What|Removed |Added Depends on||146484 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=146484 [Bug 146484] Start and End Quote windows show huge font (quotes) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146484] Start and End Quote windows show huge font (quotes)
https://bugs.documentfoundation.org/show_bug.cgi?id=146484 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||113209 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113209 [Bug 113209] [META] UI bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108430] [META] Mouse cursor bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108430 BogdanB changed: What|Removed |Added Depends on||144738 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=144738 [Bug 144738] "Fat Cross" cursor has extra shadow on Windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144738] "Fat Cross" cursor has extra shadow on Windows
https://bugs.documentfoundation.org/show_bug.cgi?id=144738 BogdanB changed: What|Removed |Added Blocks||108430 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108430 [Bug 108430] [META] Mouse cursor bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 BogdanB changed: What|Removed |Added Depends on||152223 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=152223 [Bug 152223] 7.4.3.2 Calc has a problem, some keys need [Alt] in quit dialog box. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152223] 7.4.3.2 Calc has a problem, some keys need [Alt] in quit dialog box
https://bugs.documentfoundation.org/show_bug.cgi?id=152223 BogdanB changed: What|Removed |Added Summary|7.4.3.2 Calc has a problem, |7.4.3.2 Calc has a problem, |some keys need [Alt] in |some keys need [Alt] in |quit dialog box.|quit dialog box -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152223] 7.4.3.2 Calc has a problem, some keys need [Alt] in quit dialog box.
https://bugs.documentfoundation.org/show_bug.cgi?id=152223 BogdanB changed: What|Removed |Added Blocks||98259 CC||buzea.bog...@libreoffice.or ||g Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126377] If the table includes many rows, the rows can't be selected when cursor is placed next to the table
https://bugs.documentfoundation.org/show_bug.cgi?id=126377 --- Comment #4 from BrianB --- Still present in 7.5.3.2 If i scroll with my mouse wheel, while holding the right button, it will expose more rows until the top most selected row tries to scroll beyond the visible window space. Then it negates the scroll attempt. If i select the first row with the mouse (black arrow on the left), then hold the Shift key and DownArrow, i can select additional lines successfully all the way to the bottom of the table. I tried using the down arrow while right click selecting and it did not work. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150530] FILEOPEN ODT Unable to open file created with LibreOffice (infinite layout loop)
https://bugs.documentfoundation.org/show_bug.cgi?id=150530 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||136524 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136524 [Bug 136524] [META] Performance/hang/lag/high CPU issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136524] [META] Performance/hang/lag/high CPU issues
https://bugs.documentfoundation.org/show_bug.cgi?id=136524 BogdanB changed: What|Removed |Added Depends on||150530 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150530 [Bug 150530] FILEOPEN ODT Unable to open file created with LibreOffice (infinite layout loop) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155284] Writer table rows deselect on scroll
https://bugs.documentfoundation.org/show_bug.cgi?id=155284 --- Comment #2 from BrianB --- Agreed. I just updated to the latest version, which fixed one of the issues (deselecting of rows) but the selection still does not scroll to select rows further down on the document. I will add my notes to that report. This one can be closed. Thx -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107810] [META] OLE/Embedded object bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=107810 BogdanB changed: What|Removed |Added Depends on||155301 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155301 [Bug 155301] Copying embedded Excel chart is not possible on Linux -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155301] Copying embedded Excel chart is not possible on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=155301 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||107810 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107810 [Bug 107810] [META] OLE/Embedded object bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103030] [META] Navigator sidebar deck and floating window
https://bugs.documentfoundation.org/show_bug.cgi?id=103030 BogdanB changed: What|Removed |Added Depends on||136408 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=136408 [Bug 136408] OUTLINE TRACKING keeps resetting to default (can't turn OFF) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 136408] OUTLINE TRACKING keeps resetting to default (can't turn OFF)
https://bugs.documentfoundation.org/show_bug.cgi?id=136408 BogdanB changed: What|Removed |Added Blocks||103030 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103030 [Bug 103030] [META] Navigator sidebar deck and floating window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155087] Autocorrection in Romanian applies to existing words
https://bugs.documentfoundation.org/show_bug.cgi?id=155087 --- Comment #36 from Mike Kaganski --- (In reply to cipricus from comment #35) > Trying /core/extras/source/autocorr/lang/ro/DocumentList.xml it opens an > empty file. Use extras/source/autocorr/lang/ro/DocumentList.xml - everything else you did is correct. Thank you! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155087] Autocorrection in Romanian applies to existing words
https://bugs.documentfoundation.org/show_bug.cgi?id=155087
--- Comment #35 from cipricus ---
(In reply to Mike Kaganski from comment #31)
> (In reply to cipricus from comment #30)
>
> Maybe it would be better if you just prepare a patch to fix this. For cases
> like this, you don't even need to download and build LibreOffice: this can
> be done directly in Wen UI.
>
> See
> https://libreoffice-dev.blogspot.com/2020/05/create-patch-for-libreoffice-
> directly.html if you decide to try this :)
I am giving it a try. Following the blog instructions ("Possibly, you are a
great C++ developer or conversely you write your first strings in C++ and you
want make LibreOffice better" - although only the last part applies to my case:
"you want etc" !!!), I have arrived at the stage
https://gerrit.libreoffice.org/c/core/+/151770,edit, and there, selecting
"OPEN" I I have to select file path or upload a file.
What should I do at this point? What is the link of the file?
Trying /core/extras/source/autocorr/lang/ro/DocumentList.xml it opens an empty
file.
Should I create a xml file containing the raw text of
https://opengrok.libreoffice.org/raw/core/extras/source/autocorr/lang/ro/DocumentList.xml?r=44355a90,
edit and upload?
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-commits] core.git: helpcontent2
helpcontent2 |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit d53540ffaf68d691061afcbc2ea55b47d5a81b69 Author: Andrea Gelmini AuthorDate: Mon May 15 06:56:03 2023 +0200 Commit: Gerrit Code Review CommitDate: Mon May 15 06:56:03 2023 +0200 Update git submodules * Update helpcontent2 from branch 'master' to 6c6fa59fd44ba6926e42c0eb37f6d63cf837ca04 - Fix typo Change-Id: I941edf7b6f860327d82f181a39b1c5784d6a73c1 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151737 Tested-by: Julien Nabet Reviewed-by: Julien Nabet diff --git a/helpcontent2 b/helpcontent2 index f2535c6ff09e..6c6fa59fd44b 16 --- a/helpcontent2 +++ b/helpcontent2 @@ -1 +1 @@ -Subproject commit f2535c6ff09e2afaa4c5db0a7fb6ee594a417732 +Subproject commit 6c6fa59fd44ba6926e42c0eb37f6d63cf837ca04
[Libreoffice-commits] help.git: source/text
source/text/swriter/01/0211.xhp |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) New commits: commit 6c6fa59fd44ba6926e42c0eb37f6d63cf837ca04 Author: Andrea Gelmini AuthorDate: Sun May 14 17:25:52 2023 +0200 Commit: Julien Nabet CommitDate: Mon May 15 06:56:03 2023 +0200 Fix typo Change-Id: I941edf7b6f860327d82f181a39b1c5784d6a73c1 Reviewed-on: https://gerrit.libreoffice.org/c/help/+/151737 Tested-by: Julien Nabet Reviewed-by: Julien Nabet diff --git a/source/text/swriter/01/0211.xhp b/source/text/swriter/01/0211.xhp index f9c43643e3..454d1322c9 100644 --- a/source/text/swriter/01/0211.xhp +++ b/source/text/swriter/01/0211.xhp @@ -354,7 +354,7 @@ Rename -Renames the selected object. At object creation time, %PRODUCTNAME assign an unique name to the object within the document. +Renames the selected object. At object creation time, %PRODUCTNAME assigns a unique name to the object within the document. Delete Table
[Libreoffice-bugs] [Bug 145441] infinity loop
https://bugs.documentfoundation.org/show_bug.cgi?id=145441 Michael Weghorn changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |INVALID -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145441] infinity loop
https://bugs.documentfoundation.org/show_bug.cgi?id=145441 Michael Weghorn changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155307] New: LibreOffice crashes each time
https://bugs.documentfoundation.org/show_bug.cgi?id=155307 Bug ID: 155307 Summary: LibreOffice crashes each time Product: LibreOffice Version: 7.4.6.2 release Hardware: All OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ezyl...@gmail.com Description: I bought Libreoffice 7.4.6.2 from Allele store a few days ago for my newly bought Apple iMac with M1 CPU and latest Vetura Operating systems. Whenever I want to use Libreoffice writer to write or edit a document, it crashes.I cannot work on it at all. Please fix this bug as soon as possible. I copy the crash report sent to Apple below for your reference. Since it is too long, I only past the first part here. Translated Report (Full Report Below) - Process: soffice [1268] Path: /Applications/LibreOffice.app/Contents/MacOS/soffice Identifier:org.documentfoundation.libreoffice Version: 7.4.6002 (7.4.6002) App Item ID: 1630474372 App External ID: 855383657 Code Type: ARM-64 (Native) Parent Process:launchd [1] User ID: 501 Date/Time: 2023-05-15 13:45:43.2650 +1000 OS Version:macOS 13.3.1 (22E772610a) Report Version:12 Anonymous UUID:2A2ECC49-598B-0138-979D-4974FD7C3F67 Sleep/Wake UUID: 0EA94D21-A26A-4ECB-A406-26E18D8BF18C Time Awake Since Boot: 6600 seconds Time Since Wake: 2999 seconds System Integrity Protection: enabled Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_CRASH (SIGABRT) Exception Codes: 0x, 0x Application Specific Information: abort() called Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x18a2b0724 __pthread_kill + 8 1 libsystem_pthread.dylib0x18a2e7c28 pthread_kill + 288 2 libsystem_c.dylib 0x18a1f5ae8 abort + 180 3 libuno_sal.dylib.3 0x1049944c8 (anonymous namespace)::signalHandlerFunction(int, __siginfo*, void*) (.cold.1) + 32 4 libuno_sal.dylib.3 0x104987c98 (anonymous namespace)::signalHandlerFunction(int, __siginfo*, void*) + 1060 5 libsystem_platform.dylib 0x18a316a84 _sigtramp + 56 6 libsystem_pthread.dylib0x18a2e7c28 pthread_kill + 288 7 libsystem_c.dylib 0x18a1f5ae8 abort + 180 8 libsystem_malloc.dylib 0x18a116e28 malloc_vreport + 908 9 libsystem_malloc.dylib 0x18a11a6e8 malloc_report + 64 10 libsystem_malloc.dylib 0x18a126f20 find_zone_and_free + 308 11 libuno_sal.dylib.3 0x10497371c rtl_uString_release + 52 12 libuno_cppu.dylib.30x104badbb4 cppu::idestructElements(void*, _typelib_TypeDescriptionReference*, int, int, void (*)(void*)) + 268 13 libuno_cppu.dylib.30x104bada5c cppu::idestroySequence(_sal_Sequence*, _typelib_TypeDescriptionReference*, _typelib_TypeDescription*, void (*)(void*)) + 184 14 libuno_cppu.dylib.30x104bb835c uno_type_sequence_destroy + 20 15 libvclplug_osxlo.dylib 0x1089dccdc +[AquaA11yTextAttributesWrapper createAttributedStringForElement:inOrigRange:] + 1000 16 AppKit 0x18db33cec -[NSAccessibilityAttributeAccessorInfo getParameterizedAttributeValue:forObject:withParameter:] + 72 17 AppKit 0x18db357e4 ___NSAccessibilityEntryPointValueForAttributeWithParameter_block_invoke.777 + 408 18 AppKit 0x18db30bb4 NSAccessibilityPerformEntryPointObject + 44 19 AppKit 0x18db327b4 NSAccessibilityEntryPointValueForAttributeWithParameter + 232 20 AppKit 0x18d934400 CopyParameterizedAttributeValue + 504 21 HIServices 0x18fb55678 _AXXMIGCopyParameterizedAttributeValue + 464 22 HIServices 0x18fb7c9ac _XCopyParameterizedAttributeValue + 540 23 HIServices 0x18fb3452c mshMIGPerform + 204 24 CoreFoundation 0x18a3c6ca0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 60 25 CoreFoundation 0x18a3c6bc0 __CFRunLoopDoSource1 + 520 26 CoreFoundation 0x18a3c55a0 __CFRunLoopRun + 2240 27 CoreFoundation 0x18a3c458c CFRunLoopRunSpecific + 612 28 HIToolbox 0x193bf9df4
[Libreoffice-bugs] [Bug 155253] Certain textbox is empty, however it should apparently contain text
https://bugs.documentfoundation.org/show_bug.cgi?id=155253 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155089] No way to create pivot table compact layout from scratch
https://bugs.documentfoundation.org/show_bug.cgi?id=155089 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155269] Chapter numbering mech silently changes para style numeric outline-level
https://bugs.documentfoundation.org/show_bug.cgi?id=155269 --- Comment #4 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152042] auto save conflicts with track changes in writer
https://bugs.documentfoundation.org/show_bug.cgi?id=152042 --- Comment #4 from QA Administrators --- Dear Taofeek, 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] [Bug 94259] FILEOPEN XLS Charts are vertically squashed
https://bugs.documentfoundation.org/show_bug.cgi?id=94259 --- Comment #14 from QA Administrators --- Dear Geert Closius, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89796] Bibliography entry inserted in a caption for an image, which frame happens to be the last element before page break, gets numbered as zero.
https://bugs.documentfoundation.org/show_bug.cgi?id=89796 --- Comment #11 from QA Administrators --- Dear agere, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89743] FORMATTING: Format All Comments causes black background for rest of line
https://bugs.documentfoundation.org/show_bug.cgi?id=89743 --- Comment #6 from QA Administrators --- Dear Gordo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89741] EDITING: Undo after Format All Comments only changes first comment
https://bugs.documentfoundation.org/show_bug.cgi?id=89741 --- Comment #5 from QA Administrators --- Dear Gordo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 89795] Filter Data IGNORED in PDF Export Macro
https://bugs.documentfoundation.org/show_bug.cgi?id=89795 --- Comment #6 from QA Administrators --- Dear Juraj, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 85539] SUMPRODUCT not summing multiple sheets
https://bugs.documentfoundation.org/show_bug.cgi?id=85539 --- Comment #6 from QA Administrators --- Dear DDCorley, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 86903] UI: Format > Cells > Borders preview is missing shaded ends of some diagonal line positions
https://bugs.documentfoundation.org/show_bug.cgi?id=86903 --- Comment #5 from QA Administrators --- Dear dg1727, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 77292] PDF: Export to PDF in A5 format with white left border line
https://bugs.documentfoundation.org/show_bug.cgi?id=77292 --- Comment #6 from QA Administrators --- Dear Gerard Jaryczewski, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 75517] EDITING: Format > Crop Image moves the bitmap position unexpectedly
https://bugs.documentfoundation.org/show_bug.cgi?id=75517 --- Comment #5 from QA Administrators --- Dear dg1727, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 61655] EDITING: UNDO Line Property changes does change Text Character Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=61655 --- Comment #8 from QA Administrators --- Dear Rainer Bielefeld Retired, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 72147] EDITING: Calc/Impress - Double clicking and dragging to select multiple words does not work
https://bugs.documentfoundation.org/show_bug.cgi?id=72147 --- Comment #35 from QA Administrators --- Dear Chris Shaw, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58476] Adding a signature to a document already signed by MS Word invalidates the MS Word signature
https://bugs.documentfoundation.org/show_bug.cgi?id=58476 --- Comment #6 from QA Administrators --- Dear Chris Rae [MSFT], To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 50349] Toolbar controls set font for Far-East text
https://bugs.documentfoundation.org/show_bug.cgi?id=50349 --- Comment #6 from QA Administrators --- Dear Yike, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 49879] MAILMERGE - Looks as if Added extra carriage return for each line with HTML mail
https://bugs.documentfoundation.org/show_bug.cgi?id=49879 --- Comment #10 from QA Administrators --- Dear Ferry Toth, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 58442] If Microsoft Word adds another signature to document originally signed by LibreOffice it causes LibreOffice to prompt saying file is corrupt
https://bugs.documentfoundation.org/show_bug.cgi?id=58442 --- Comment #13 from QA Administrators --- Dear Chris Rae [MSFT], To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 46187] Can't Connect Simultaneously Connect through Different JDBC Drivers
https://bugs.documentfoundation.org/show_bug.cgi?id=46187 --- Comment #8 from QA Administrators --- Dear Ken Diederich, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 43609] failing c++ based subsequenttest: ScDataPilotFieldObj::XDataPilotFieldGrouping::createDateGrouping
https://bugs.documentfoundation.org/show_bug.cgi?id=43609 --- Comment #8 from QA Administrators --- Dear Markus Mohrhard, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 47047] [FORMATTING, FILESAVE] Paragraph spacing not properly exported to xls in comments
https://bugs.documentfoundation.org/show_bug.cgi?id=47047 --- Comment #9 from QA Administrators --- Dear Nicolas Mailhot, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 44669] Setting "Display Zero Values" and "Value highlighting" without effect for CALC OLE objects VIEWING
https://bugs.documentfoundation.org/show_bug.cgi?id=44669 --- Comment #9 from QA Administrators --- Dear bugzilla, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 42871] Command line conversion of html to pdf using convert to produces pdfs that don't look like html
https://bugs.documentfoundation.org/show_bug.cgi?id=42871 --- Comment #12 from QA Administrators --- Dear Rob Hutton, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142141] Line numbers are not available in tabbed user interface
https://bugs.documentfoundation.org/show_bug.cgi?id=142141 --- Comment #2 from QA Administrators --- Dear flylix, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126144] Make font sizes in Autofilter window the same for 125% scaling
https://bugs.documentfoundation.org/show_bug.cgi?id=126144 --- Comment #8 from QA Administrators --- Dear Roman Kuznetsov, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 126009] Increasing margin size does not reflect new constraints for header values without closing and reopening the Page Style dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=126009 --- Comment #7 from QA Administrators --- Dear Ormes Liivak, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153789] Icons needed for new Uno commands WatchWindow and StackWindow in the Basic IDE
https://bugs.documentfoundation.org/show_bug.cgi?id=153789 --- Comment #6 from Commit Notification --- Rizal Muttaqin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/73b35219cc9ed42072506ed18a5767f072e1da02 tdf#153789 Breeze icons for Watched Expressions and Call Stack It will be available in 7.6.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: icon-themes/breeze icon-themes/breeze_dark icon-themes/breeze_dark_svg icon-themes/breeze_svg
icon-themes/breeze/cmd/32/stackwindow.png |binary icon-themes/breeze/cmd/32/watchwindow.png |binary icon-themes/breeze/cmd/lc_stackwindow.png |binary icon-themes/breeze/cmd/lc_watchwindow.png |binary icon-themes/breeze/cmd/sc_stackwindow.png |binary icon-themes/breeze/cmd/sc_watchwindow.png |binary icon-themes/breeze_dark/cmd/32/stackwindow.png |binary icon-themes/breeze_dark/cmd/32/watchwindow.png |binary icon-themes/breeze_dark/cmd/lc_stackwindow.png |binary icon-themes/breeze_dark/cmd/lc_watchwindow.png |binary icon-themes/breeze_dark/cmd/sc_stackwindow.png |binary icon-themes/breeze_dark/cmd/sc_watchwindow.png |binary icon-themes/breeze_dark_svg/cmd/32/stackwindow.svg |1 + icon-themes/breeze_dark_svg/cmd/32/watchwindow.svg |1 + icon-themes/breeze_dark_svg/cmd/lc_stackwindow.svg |1 + icon-themes/breeze_dark_svg/cmd/lc_watchwindow.svg |1 + icon-themes/breeze_dark_svg/cmd/sc_stackwindow.svg |1 + icon-themes/breeze_dark_svg/cmd/sc_watchwindow.svg |1 + icon-themes/breeze_svg/cmd/32/stackwindow.svg |1 + icon-themes/breeze_svg/cmd/32/watchwindow.svg |1 + icon-themes/breeze_svg/cmd/lc_stackwindow.svg |1 + icon-themes/breeze_svg/cmd/lc_watchwindow.svg |1 + icon-themes/breeze_svg/cmd/sc_stackwindow.svg |1 + icon-themes/breeze_svg/cmd/sc_watchwindow.svg |1 + 24 files changed, 12 insertions(+) New commits: commit 73b35219cc9ed42072506ed18a5767f072e1da02 Author: Rizal Muttaqin AuthorDate: Mon May 15 05:03:25 2023 +0700 Commit: Rizal Muttaqin CommitDate: Mon May 15 03:22:16 2023 +0200 tdf#153789 Breeze icons for Watched Expressions and Call Stack Change-Id: Iff094c8101a9d01fd1f73cf66c8672d0e8eb3938 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151750 Tested-by: Jenkins Reviewed-by: Rizal Muttaqin diff --git a/icon-themes/breeze/cmd/32/stackwindow.png b/icon-themes/breeze/cmd/32/stackwindow.png new file mode 100644 index ..029c408081b3 Binary files /dev/null and b/icon-themes/breeze/cmd/32/stackwindow.png differ diff --git a/icon-themes/breeze/cmd/32/watchwindow.png b/icon-themes/breeze/cmd/32/watchwindow.png new file mode 100644 index ..da0a1ea8960f Binary files /dev/null and b/icon-themes/breeze/cmd/32/watchwindow.png differ diff --git a/icon-themes/breeze/cmd/lc_stackwindow.png b/icon-themes/breeze/cmd/lc_stackwindow.png new file mode 100644 index ..2399acccdc4d Binary files /dev/null and b/icon-themes/breeze/cmd/lc_stackwindow.png differ diff --git a/icon-themes/breeze/cmd/lc_watchwindow.png b/icon-themes/breeze/cmd/lc_watchwindow.png new file mode 100644 index ..7dc0a7b68ce5 Binary files /dev/null and b/icon-themes/breeze/cmd/lc_watchwindow.png differ diff --git a/icon-themes/breeze/cmd/sc_stackwindow.png b/icon-themes/breeze/cmd/sc_stackwindow.png new file mode 100644 index ..9fde9b8b16cf Binary files /dev/null and b/icon-themes/breeze/cmd/sc_stackwindow.png differ diff --git a/icon-themes/breeze/cmd/sc_watchwindow.png b/icon-themes/breeze/cmd/sc_watchwindow.png new file mode 100644 index ..14da3a4d266f Binary files /dev/null and b/icon-themes/breeze/cmd/sc_watchwindow.png differ diff --git a/icon-themes/breeze/startmath/res/co21901.png b/icon-themes/breeze/starmath/res/co21901.png similarity index 100% rename from icon-themes/breeze/startmath/res/co21901.png rename to icon-themes/breeze/starmath/res/co21901.png diff --git a/icon-themes/breeze/startmath/res/mi22016.png b/icon-themes/breeze/starmath/res/mi22016.png similarity index 100% rename from icon-themes/breeze/startmath/res/mi22016.png rename to icon-themes/breeze/starmath/res/mi22016.png diff --git a/icon-themes/breeze/startmath/res/mi22017.png b/icon-themes/breeze/starmath/res/mi22017.png similarity index 100% rename from icon-themes/breeze/startmath/res/mi22017.png rename to icon-themes/breeze/starmath/res/mi22017.png diff --git a/icon-themes/breeze/startmath/res/mi22018.png b/icon-themes/breeze/starmath/res/mi22018.png similarity index 100% rename from icon-themes/breeze/startmath/res/mi22018.png rename to icon-themes/breeze/starmath/res/mi22018.png diff --git a/icon-themes/breeze/startmath/res/mi22019.png b/icon-themes/breeze/starmath/res/mi22019.png similarity index 100% rename from icon-themes/breeze/startmath/res/mi22019.png rename to icon-themes/breeze/starmath/res/mi22019.png diff --git a/icon-themes/breeze_dark/cmd/32/stackwindow.png b/icon-themes/breeze_dark/cmd/32/stackwindow.png new file mode 100644 index ..f608fd5f05cd Binary files /dev/null and b/icon-themes/breeze_dark/cmd/32/stackwindow.png differ diff --git a/icon-themes/breeze_dark/cmd/32/watchwindow.png b/icon-themes/breeze_dark/cmd/32/watchwindow.png new file mode 100644 index ..4b2414d86f06 Binary files /dev/null and
[Libreoffice-bugs] [Bug 155306] New: Incorrect footnotes numbering by page for columns configuration
https://bugs.documentfoundation.org/show_bug.cgi?id=155306 Bug ID: 155306 Summary: Incorrect footnotes numbering by page for columns configuration Product: LibreOffice Version: 7.4.6.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hudson...@gmail.com Description: When I insert footnotes in a text in two columns, the number and disposition of footnotes are incorrect. Steps to Reproduce: 1. Insert dummy text into one page only. 2. Configure that text in two columns. 3. Go to Tools->Footnotes and Endnotes. 4. Configure numbering footnotes by page. 5. Insert two footnotes in that text. Actual Results: The footnote numbering is incorrect (usually starting on 0 and not incrementing). Expected Results: Numbering correct. Reproducible: Always User Profile Reset: No Additional Info: None. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'feature/cib_contract57d' - sw/qa sw/source
sw/qa/extras/htmlexport/htmlexport.cxx | 42 -
sw/source/filter/html/htmlatr.cxx |3 +-
2 files changed, 38 insertions(+), 7 deletions(-)
New commits:
commit ba97c0bf8f1c47cb360dc771632cb04cb9f0b04a
Author: Miklos Vajna
AuthorDate: Thu Nov 7 17:17:35 2019 +0100
Commit: Thorsten Behrens
CommitDate: Mon May 15 00:51:39 2023 +0200
sw XHTML export: can't have character children
Fixes the following reqif-xhtml validation error:
ERROR at 214: [XSD] cvc-complex-type.2.3: Element 'reqif-xhtml:blockquote'
cannot have character [children], because the type's content type is
element-only.
But this is probably useful in the general xhtml case as well.
[ Also add a way to not load a document when we want to cover "store"
behavior in a test. ]
Change-Id: I88795271475863b9560ac1cb99636c507746f1e9
Reviewed-on: https://gerrit.libreoffice.org/82239
Reviewed-by: Miklos Vajna
Tested-by: Jenkins
diff --git a/sw/qa/extras/htmlexport/htmlexport.cxx
b/sw/qa/extras/htmlexport/htmlexport.cxx
index 3eee4c223890..00b5f511002f 100644
--- a/sw/qa/extras/htmlexport/htmlexport.cxx
+++ b/sw/qa/extras/htmlexport/htmlexport.cxx
@@ -38,11 +38,11 @@ public:
* Wraps a reqif-xhtml fragment into an XHTML file, so an XML parser can
* parse it.
*/
-void wrapFragment(SvMemoryStream& rStream)
+static void wrapFragment(const utl::TempFile& rTempFile, SvMemoryStream&
rStream)
{
rStream.WriteCharPtr(
"http://www.w3.org/1999/xhtml\;>\n");
-SvFileStream aFileStream(maTempFile.GetURL(), StreamMode::READ);
+SvFileStream aFileStream(rTempFile.GetURL(), StreamMode::READ);
rStream.WriteStream(aFileStream);
rStream.WriteCharPtr("\n");
rStream.Seek(0);
@@ -102,6 +102,11 @@ private:
#define DECLARE_HTMLEXPORT_ROUNDTRIP_TEST(TestName, filename)
DECLARE_SW_ROUNDTRIP_TEST(TestName, filename, nullptr, HtmlExportTest)
+/// HTML export of the sw doc model tests.
+class SwHtmlDomExportTest : public SwModelTestBase, public HtmlTestTools
+{
+};
+
DECLARE_HTMLEXPORT_ROUNDTRIP_TEST(testFdo81276, "fdo81276.html")
{
uno::Reference
xPageStyles(getStyles("PageStyles"));
@@ -572,7 +577,7 @@ DECLARE_HTMLEXPORT_ROUNDTRIP_TEST(testReqIfOle2,
"reqif-ole2.xhtml")
{
// Check that the replacement graphic is exported at RTF level.
SvMemoryStream aStream;
-wrapFragment(aStream);
+wrapFragment(maTempFile, aStream);
xmlDocPtr pDoc = parseXmlStream();
CPPUNIT_ASSERT(pDoc);
// Get the path of the RTF data.
@@ -635,7 +640,7 @@ DECLARE_HTMLEXPORT_TEST(testTransparentImage,
"transparent-image.odt")
DECLARE_HTMLEXPORT_TEST(testTransparentImageReqIf, "transparent-image.odt")
{
SvMemoryStream aStream;
-wrapFragment(aStream);
+wrapFragment(maTempFile, aStream);
xmlDocPtr pDoc = parseXmlStream();
CPPUNIT_ASSERT(pDoc);
@@ -652,7 +657,7 @@ DECLARE_HTMLEXPORT_TEST(testOleNodataReqIf,
"reqif-ole-nodata.odt")
{
// This failed, io::IOException was thrown during the filter() call.
SvMemoryStream aStream;
-wrapFragment(aStream);
+wrapFragment(maTempFile, aStream);
xmlDocPtr pDoc = parseXmlStream();
CPPUNIT_ASSERT(pDoc);
@@ -667,7 +672,7 @@ DECLARE_HTMLEXPORT_TEST(testOleNodataReqIf,
"reqif-ole-nodata.odt")
DECLARE_HTMLEXPORT_TEST(testNoLangReqIf, "reqif-no-lang.odt")
{
SvMemoryStream aStream;
-wrapFragment(aStream);
+wrapFragment(maTempFile, aStream);
xmlDocPtr pDoc = parseXmlStream();
CPPUNIT_ASSERT(pDoc);
@@ -691,6 +696,31 @@ DECLARE_HTMLEXPORT_TEST(testFieldShade, "field-shade.odt")
assertXPath(pDoc, "/html/body/p[2]/span/span", 0);
}
+CPPUNIT_TEST_FIXTURE(SwHtmlDomExportTest, testBlockQuoteReqIf)
+{
+// Build a document model that uses the Quotations paragraph style.
+loadURL("private:factory/swriter", nullptr);
+uno::Reference xParagraph(getParagraph(1),
uno::UNO_QUERY);
+xParagraph->setPropertyValue("ParaStyleName",
uno::makeAny(OUString("Quotations")));
+
+// Export it.
+uno::Reference xStorable(mxComponent, uno::UNO_QUERY);
+utl::MediaDescriptor aMediaDescriptor;
+aMediaDescriptor["FilterName"] <<= OUString("HTML (StarWriter)");
+aMediaDescriptor["FilterOptions"] <<= OUString("xhtmlns=reqif-xhtml");
+xStorable->storeToURL(maTempFile.GetURL(),
aMediaDescriptor.getAsConstPropertyValueList());
+SvMemoryStream aStream;
+HtmlExportTest::wrapFragment(maTempFile, aStream);
+xmlDocPtr pDoc = parseXmlStream();
+CPPUNIT_ASSERT(pDoc);
+
+// Without the accompanying fix in place, this test would have failed with:
+// - Expected: 1
+// - Actual : 0
+// i.e. had character (direct) children, which is invalid
xhtml.
+assertXPath(pDoc,
"/reqif-xhtml:html/reqif-xhtml:div/reqif-xhtml:blockquote/reqif-xhtml:p", 1);
+}
+
[Libreoffice-bugs] [Bug 139963] "Delete spaces and tabs at end and start of line" option in AutoCorrect needs critical evaluation
https://bugs.documentfoundation.org/show_bug.cgi?id=139963 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Version|7.2.0.0.alpha0+ |Inherited From OOo CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 --- Comment #2 from Stéphane Guillou (stragu) --- Thanks Seth, confirmed that it is not functional in: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Same in OOo 3.3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 132399] Colibre: Too large size for Impress' Display Views icons
https://bugs.documentfoundation.org/show_bug.cgi?id=132399 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||122245 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=122245 [Bug 122245] [META] Icon theme issues that need coding -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 122245] [META] Icon theme issues that need coding
https://bugs.documentfoundation.org/show_bug.cgi?id=122245 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||132399 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=132399 [Bug 132399] Colibre: Too large size for Impress' Display Views icons -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148154] Reordering Conditional Formats in Manage CF dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=148154 --- Comment #4 from Alistair Saywell --- Following comments on https://ask.libreoffice.org/t/calc-how-to-change-conditional-formatting-priority/91488 it seems that the list of conditions is purely alphabetical and does not indicate precedence. In Manage Conditional Formatting it looks as if the Highlighted condition is first in order of applying. For most users, including myself until today, it is not immediately obvious which condition takes precedence just from the appearance of the Manage Conditional Formatting dialogue. This is also against the expectation of the original bug post. Sample with differing order of creation at https://ask.libreoffice.org/t/calc-how-to-change-conditional-formatting-priority/91488/6?u=earnestal -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155269] Chapter numbering mech silently changes para style numeric outline-level
https://bugs.documentfoundation.org/show_bug.cgi?id=155269 --- Comment #3 from R. Bingham --- (In reply to Mike Kaganski from comment #2) Ah, ah! This is good. Reviewing bugs 129270, 129668, 129669 and 140846 I see continuing *conceptual* confusion even among the LO Dev Team. If this is "simple user confusion" then tell me why does it persist for this feature? Noting the MK comment https://bugs.documentfoundation.org/show_bug.cgi?id=140846#c4 (LOL, LOL) about good intentions, I suggest a part of the confusion persistence is that through incremental behavior and UI changes over the years in response to point bugs or enhancement requests regards levels, etc., those Dev Team responses, perhaps at best only lightly analyzed for conceptual and user experience consistency, have created a divergence between observed functional behavior (implementation) and observed *presentation* (the UI). Users are responding to that disagreement with confusion and will continue that confusion until that divergence is reconciled away. Let us see how this plays out in the present issue. This will be long because I am setting up user POV experience and mental-model concepts. Mental-model of Styles >From a statement somewhere in the user-facing documentation (UFD), LO Writer is a **style** oriented document creation app. Most if not all visible document objects have an associated style-object that governs the textual and graphical presentation of the object. That association is a link to a style-object global to the document. We wave away nuances and complications from visible-object-local, anonymous style-object clones created by per-visible-object manual interventions. In theory, a change to a global style-object affects all linked document-visible objects (practice a different matter). Global style-objects have an existence observedly independent of being applied to any visible document object. A user can access the global style-objects for understanding, for config maintenance or to create new via Navigator. Here we focus on style-object sub-types (as presented in user POV Navigator UI they are peer sub-types) Paragraph and List. From observation, functionally List seems an enhancement on, or perhaps a wrapper of, Paragraph. [Paragraph Style] (PS) feature >From observation, the PS tabbed-widget UI presents as the fullest-featured way to initially define/configure/update the properties of a PS-object. One of the PS style-object properties prominently managed via the UI is a sub-object identified as tab[Outline]->Outline->[Outline level:]. The value-assignment picklist for this sub-object offers 11 values: an ordered list of integer values 1 -- 10 and a mysterious non-integer "Text Body." >From observation, [Outline level:] seems important to the update behavior of the Document field variable Chapter->name, and perhaps other Writer features. Indeed, fiddling the value of [Outline level:] in global PS Foo changes how Chapter->name updates when scan-encountering paragraphs of PS Foo. Note the "sequential scan" mental model of how the document text is processed. [List Style] (LS) feature >From observation, the LS tabbed-widget UI presents as the fullest-featured way to initially define/configure/update the properties of a List style-object. Two tabs of that UI (tabs [Position] and [Customize]) present something visually on the left labeled a "Level." This Level thingy appears to be an integer-valued (1 -- 10) index for identifying a *set* of properties that instruct the construction of a sub-string of the final List-feature text output string prepended to visible, List style-object-linked paragraphs in the document. So 10 possible property sets in all. From observation, this integer index orders a rank relationship for resetting an implied numerical counter associated with each property set, and ordering the sub-string output from property sets in ascending integer value for (presumably language dependent) left-to-right concatenation in to the final List-feature output text string. >From observation, the LS->Level integer-values domain and the PS->[Outline level:] integer-values domain are mutually independent. That is, fiddling the PS->[Outline level:] value of a para assigned a list-style in PS->tab[Outline]->[Apply List Style]->[List style:] or manually set to a LS context does not seem to change what the LS feature does in presentation of the para text. LS->[Level] does not seem to be an explicitly exposed or picklist settable property of a given List style-object in the model of PS->[Outline level:]. Rather, the LS UI display index seems to only serve as an internal, organizing index for the List style-object feature. OTOH, fiddling PS->tab[Outline]->[Apply List Style]->[List style:] picklist value *does* change the List-feature textual presentation. So now we have the PS->[Outline] strongly presented as a config manager one of two features that involve some concept of mutually independent sets of **levels**.
[Libreoffice-bugs] [Bug 57823] EDITING: Insert/OverWrite Mode inoperative
https://bugs.documentfoundation.org/show_bug.cgi?id=57823 Aron Budea changed: What|Removed |Added CC||ma...@mashpot.net --- Comment #5 from Aron Budea --- *** Bug 153893 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Bug 83946 depends on bug 153893, which changed state. Bug 153893 Summary: Insert / Override mode not working whilst Track Changes is set to Record https://bugs.documentfoundation.org/show_bug.cgi?id=153893 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153893] Insert / Override mode not working whilst Track Changes is set to Record
https://bugs.documentfoundation.org/show_bug.cgi?id=153893 Aron Budea changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #3 from Aron Budea --- Looks like a duplicate of 153893. *** This bug has been marked as a duplicate of bug 57823 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 83946] [META] Tracking changes issues
https://bugs.documentfoundation.org/show_bug.cgi?id=83946 Aron Budea changed: What|Removed |Added Depends on||57823 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=57823 [Bug 57823] EDITING: Insert/OverWrite Mode inoperative -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 57823] EDITING: Insert/OverWrite Mode inoperative
https://bugs.documentfoundation.org/show_bug.cgi?id=57823 Aron Budea changed: What|Removed |Added Blocks||83946 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=83946 [Bug 83946] [META] Tracking changes issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155224] Libreoffice Writer Freezes and Crashes with multiple windows open
https://bugs.documentfoundation.org/show_bug.cgi?id=155224 --- Comment #9 from agap...@hotmail.com --- (In reply to Stéphane Guillou (stragu) from comment #5) > (In reply to agapp11 from comment #4) > > I use only MS fonts but also LanguageTool and Zotero extension. Maybe those > > are the culprits? > > If you've tested with a new profile (Help > Restart in Safe mode > Reset to > factory setting (with both options ticked) > Apply changes and restart) and > could still reproduce the issue, it should be unrelated to the extensions. > > Do you see a crash reporter window when you restart LO? If so, please report > the crash and share the link that the dialog gives you. > > And do you still experience bug 154978 with LO 7.5.3? It seems the crash has returned. I reset my profile and reinstalled the extensions. I was trying to write "Plants have developed many chemical methods to deter heterotrophes from eat..." when writer freezes and then I get the following dialog: https://i.imgur.com/LgL4b7p.png The document is attached. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155224] Libreoffice Writer Freezes and Crashes with multiple windows open
https://bugs.documentfoundation.org/show_bug.cgi?id=155224 --- Comment #8 from agap...@hotmail.com --- Created attachment 187283 --> https://bugs.documentfoundation.org/attachment.cgi?id=187283=edit MY LO Writer document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-commits] core.git: Branch 'feature/cib_contract57d' - 16 commits - configure.ac connectivity/source download.lst embeddedobj/source external/curl external/hsqldb formula/source include/sv
configure.ac |2
connectivity/source/drivers/hsqldb/HDriver.cxx | 31
download.lst | 20 +--
embeddedobj/source/commonembedding/embedobj.cxx | 60 -
embeddedobj/source/commonembedding/specialobject.cxx |9 +
embeddedobj/source/inc/commonembobj.hxx |3
embeddedobj/source/inc/specialobject.hxx |7 +
external/curl/curl-7.26.0_win-proxy.patch|9 -
external/curl/curl-msvc-disable-protocols.patch.1|2
external/curl/curl-nss.patch.1 |6
external/curl/zlib.patch.0 | 12 -
external/hsqldb/UnpackedTarball_hsqldb.mk|1
external/hsqldb/patches/disable-dump-script.patch| 14 ++
formula/source/core/api/token.cxx| 13 --
include/svx/svdoole2.hxx | 17 ++
include/svx/unoshape.hxx |2
sc/source/core/inc/interpre.hxx | 12 +
sc/source/core/tool/interpr1.cxx |4
sc/source/core/tool/interpr3.cxx |4
sc/source/core/tool/interpr4.cxx | 10 +
sc/source/ui/docshell/documentlinkmgr.cxx|9 +
sfx2/source/doc/iframe.cxx | 69 ++
svx/source/svdraw/svdoole2.cxx | 123 ++-
svx/source/unodraw/shapeimpl.hxx |5
svx/source/unodraw/unoshap4.cxx | 23 +++
sw/inc/ndole.hxx |4
sw/qa/extras/htmlexport/htmlexport.cxx | 16 +-
sw/source/core/inc/frmtool.hxx |1
sw/source/core/layout/flowfrm.cxx| 20 +++
sw/source/core/layout/sectfrm.cxx|3
sw/source/core/ole/ndole.cxx | 99 +--
xmloff/source/draw/ximpshap.cxx | 29
xmloff/source/draw/ximpshap.hxx |2
33 files changed, 493 insertions(+), 148 deletions(-)
New commits:
commit 2bcf1b7c21ef9b343c148d4e11566b868321d5d2
Author: Caolán McNamara
AuthorDate: Thu Apr 20 20:58:21 2023 +0100
Commit: Thorsten Behrens
CommitDate: Mon May 15 00:06:27 2023 +0200
assume IFrame script/macro support isn't needed
seems undocumented at least
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/151020
Tested-by: Jenkins
Reviewed-by: Xisco Fauli
(cherry picked from commit a10a5994bddf7646196ff45f6af598420d8663ad)
Change-Id: I316e4f4f25ddb7cf6b7bac4d856a721b987207a3
diff --git a/sfx2/source/doc/iframe.cxx b/sfx2/source/doc/iframe.cxx
index 621f728edea9..12ea3b104a20 100644
--- a/sfx2/source/doc/iframe.cxx
+++ b/sfx2/source/doc/iframe.cxx
@@ -167,20 +167,16 @@ sal_Bool SAL_CALL IFrameObject::load(
uno::Reference < util::XURLTransformer > xTrans(
util::URLTransformer::create( mxContext ) );
xTrans->parseStrict( aTargetURL );
+INetURLObject aURLObject(aTargetURL.Complete);
+if (aURLObject.GetProtocol() == INetProtocol::Macro ||
aURLObject.isSchemeEqualTo(u"vnd.sun.star.script"))
+return false;
+
uno::Reference xParentFrame =
xFrame->getCreator();
SfxObjectShell* pDoc = SfxMacroLoader::GetObjectShell(xParentFrame);
-if (INetURLObject(aTargetURL.Complete).GetProtocol() ==
INetProtocol::Macro)
-{
-if (pDoc && !pDoc->AdjustMacroMode())
-return false;
-}
-
bool bUpdateAllowed(true);
if (pDoc)
{
-// perhaps should only check for file targets, but lets default to
making it strong
-// unless there is a known need to distinguish
comphelper::EmbeddedObjectContainer& rEmbeddedObjectContainer =
pDoc->getEmbeddedObjectContainer();
bUpdateAllowed =
rEmbeddedObjectContainer.getUserAllowsLinkUpdate();
}
commit 302b47e2631deaf007bcb6240d31f22d9eeb5359
Author: Caolán McNamara
AuthorDate: Thu Apr 13 11:31:17 2023 +0100
Commit: Thorsten Behrens
CommitDate: Sun May 14 23:59:51 2023 +0200
put floating frames under managed links control
like we do for sections and ole objects that link to their content
individual commits in trunk are:
extract a OCommonEmbeddedObject::SetInplaceActiveState for reuse
no behaviour change intended
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150341
Tested-by: Caolán McNamara
Reviewed-by: Caolán McNamara
(cherry picked from commit 183e34a3f8c429c0698951e24c17844e416a3825)
use parent window as dialog parent
it makes no odds, but is more convenient for upcoming modification
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/150342
Tested-by: Caolán McNamara
[Libreoffice-bugs] [Bug 155305] A double click event in a cell does not work because a comment is too long in another cell
https://bugs.documentfoundation.org/show_bug.cgi?id=155305 --- Comment #1 from Carlos Codina --- Created attachment 187282 --> https://bugs.documentfoundation.org/attachment.cgi?id=187282=edit the file with macros where the problem can be reproduced -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155305] New: A double click event in a cell does not work because a comment is too long in another cell
https://bugs.documentfoundation.org/show_bug.cgi?id=155305 Bug ID: 155305 Summary: A double click event in a cell does not work because a comment is too long in another cell Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jccod...@hotmail.com Description: Very strange problem in my complex spreadsheet due to a long comment in a cell. Unbelievable Please enable de macros and try to reproduce the steps. You can use a virtual machine if you don't trust my macros It is very complex to reproduce from scratch, so I need to send you the XLSM file that works fine with Microsoft. Please request me the file, because I cannot see here any place to attach the file Steps to Reproduce: 1.Open the file I want to attach but there is no option. Please request me the file 2.Accept the popup message shown 3.Press the '>>> CALCULAR <<<' button on the first row 4.Accept the popup message shown 5.Perform a double click event over the cell 13-F 6.It will appears something like a tooltip message. Close it 7.Perform a double click event over the cell 5-F 8.It should appear something similar to step 6, but it appears a formula 9.Remove the existing comment in cell 2-D 10.Perform again a double click event over the cell 5-F 11.Then you can check the expected message, like in step 6. -> the double click event is not executed due to the long comment in cell 2D I can provide a video Actual Results: Step 8 is wrong Expected Results: double click working for all cells Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: es Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
Infra call on Tue, May 16 at 16:30 UTC
Hi there, The next infra call will take place at `date -d "Tue, 16 May 2023 16:30 UTC"` (18:30 Berlin time). We'll meet at https://jitsi.documentfoundation.org/infra and write the minutes to https://pad.documentfoundation.org/p/infra . Agenda TBA. See you there! Cheers, -- Guilhem. signature.asc Description: PGP signature
[Libreoffice-bugs] [Bug 155304] Bullets disappeared in old ODP presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=155304 m.a.riosv changed: What|Removed |Added Version|4.0.0.3 release |3.6.7.2 release CC||miguelangelrv@libreoffice.o ||rg --- Comment #2 from m.a.riosv --- Reproducible Versión 3.6.7.2 (ID de compilación: e183d5b) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108629] [META] Ruler bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108629 Bug 108629 depends on bug 154904, which changed state. Bug 154904 Summary: Tabulators defined for a paragraph are not displayed in the horizontal ruler https://bugs.documentfoundation.org/show_bug.cgi?id=154904 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |DUPLICATE -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154904] Tabulators defined for a paragraph are not displayed in the horizontal ruler
https://bugs.documentfoundation.org/show_bug.cgi?id=154904 Gabor Kelemen (allotropia) changed: What|Removed |Added CC||kelem...@ubuntu.com Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #4 from Gabor Kelemen (allotropia) --- I agree this is a duplicate, since same bibisect result. *** This bug has been marked as a duplicate of bug 154035 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154035] It is not possible to set tabs in Writer by clicking on the top ruler (GTK3?)
https://bugs.documentfoundation.org/show_bug.cgi?id=154035 --- Comment #5 from Gabor Kelemen (allotropia) --- *** Bug 154904 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146134] Difficulty creating mail labels
https://bugs.documentfoundation.org/show_bug.cgi?id=146134 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| --- Comment #1 from Stéphane Guillou (stragu) --- Hi John Could you please provide more precise steps to reproduce the issue you experienced? If at all possible, with example files to test if we can reproduce the same problem with the database not populating the fields properly. Much appreciated. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145376] Separate pages too hard to see in page panel
https://bugs.documentfoundation.org/show_bug.cgi?id=145376 --- Comment #23 from Stéphane Guillou (stragu) --- For what it's worth, an unrelated report show us the same issue in attachment 177463 of bug 146701, using LO 7.2. Jim, it would be good to test with a currently supported version, preferably LO 7.5, to see if the issue remains. Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 146701] Button size issue in Shapes sidebar in high DPI environments.
https://bugs.documentfoundation.org/show_bug.cgi?id=146701 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEEDINFO --- Comment #2 from Stéphane Guillou (stragu) --- Thank you for the report, Tokai. Could you please test a currently-supported version (preferably 7.5) and let us know if you can still reproduce the same issue? If you do, please paste here the information copied from Help > About LibreOffice. Much appreciated! -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155291] UI Linux KDE/QT/X11 : Unable to drag sheet tabs in Calc (or drag to layer tabs in Draw) - possibly already fixed in 7.5.3.1
https://bugs.documentfoundation.org/show_bug.cgi?id=155291 --- Comment #3 from Stéphane Guillou (stragu) --- (In reply to alex from comment #2) > Thanks Stéphane, I had noticed it a few times and finally got around to > reporting it. > Clearly the team was much better organised than me! > Thanks for the great work. Thank you for taking the time to report issues! All the best. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155304] New: Bullets disappeared in old ODP presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=155304 Bug ID: 155304 Summary: Bullets disappeared in old ODP presentation Product: LibreOffice Version: 4.0.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: filters and storage Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: stephane.guil...@libreoffice.org Steps: 1. Open attachment 164229 Results: bullets are gone. Regression as, according to bug 135288 comment 1, was not reproduced in 3.6 but reproduced in 4.0. I can confirm that bullets were there in OOo 3.3, but are still not visible in: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151248] [META] Regressions from switching to FastParser
https://bugs.documentfoundation.org/show_bug.cgi?id=151248 Stéphane Guillou (stragu) changed: What|Removed |Added Version|unspecified |6.1.0.3 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155304] Bullets disappeared in old ODP presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=155304 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||5288 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135288] Bullets disappeared in old SXI presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=135288 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||5304 CC||michael.me...@collabora.com ||, noelgran...@gmail.com, ||stephane.guillou@libreoffic ||e.org Regression By||Mohammed Abdul Azeem Summary|Bullets disappeared in old |Bullets disappeared in old |presentations |SXI presentation OS|other |All Version|4.0.0.3 release |6.1.0.3 release --- Comment #8 from Stéphane Guillou (stragu) --- We've got two different issues here, that appeared at different times. Regarding what raal bibisected with the SXI file, I can confirm that bullets are present in: Version: 6.0.0.3 Build ID: 64a0f66915f38c6217de274f0aa8e15618924765 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group But they are gone in: Version: 6.1.0.3 Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk2; Locale: en-AU (en_AU.UTF-8); Calc: group threaded As that's the one that was bibisected, let's focus the report on it. Still repro in recent master build: Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: b5a22fceed57f05eb43a5fb0817afbc141610c5e CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Regarding the ODP file, I have created bug 155304 to track separately. Noel and Michael, just thought I'd copy you in as Mohammed's mentors, in case you have an idea. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155304] Bullets disappeared in old ODP presentation
https://bugs.documentfoundation.org/show_bug.cgi?id=155304 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Blocks||48799 Status|UNCONFIRMED |NEW Keywords||bibisectRequest, ||filter:odp, regression --- Comment #1 from Stéphane Guillou (stragu) --- (Report is a split from bug 135288. Marking as new as confirmed there.) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=48799 [Bug 48799] [META] Impress Bullets and Numbering bugs (formatting and UI) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 48799] [META] Impress Bullets and Numbering bugs (formatting and UI)
https://bugs.documentfoundation.org/show_bug.cgi?id=48799 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||155304 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155304 [Bug 155304] Bullets disappeared in old ODP presentation -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155303] Asking for a new functionality: to draw or handwrite in Impress or Write
https://bugs.documentfoundation.org/show_bug.cgi?id=155303 Eyal Rozenberg changed: What|Removed |Added Blocks||102016 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102016 [Bug 102016] [META] Windows 10 Tablet Mode issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102016] [META] Windows 10 Tablet Mode issues
https://bugs.documentfoundation.org/show_bug.cgi?id=102016 Eyal Rozenberg changed: What|Removed |Added Depends on||155303 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=155303 [Bug 155303] Asking for a new functionality: to draw or handwrite in Impress or Write -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155303] Asking for a new functionality: to draw or handwrite in Impress or Write
https://bugs.documentfoundation.org/show_bug.cgi?id=155303 Eyal Rozenberg changed: What|Removed |Added Severity|normal |enhancement --- Comment #1 from Eyal Rozenberg --- (In reply to puigpuig from comment #0) I'm not sure I understand what you're asking for. What is a "tab to draw"? Can you post a screenshot, or link to a video, of a "tab to draw" in another application? -- You are receiving this mail because: You are the assignee for the bug.
GSOC '23 : Convert Writer's Java UNO API tests to C++
Hey everyone, I am Dipam Turkar, currently pursuing B.Tech in Computer Science and Engineering at IIT Mandi, India. I am thrilled to share with you that I will be working with LibreOffice this summer on the project 'Convert Writer's Java UNO API tests to C++' as mentioned here https://summerofcode.withgoogle.com/proposals/details/QBLttE0T. The project aims to convert the UNO API tests for LibreOffice Writer which are written in Java to C++. The unit tests for Writer’s UNO API which were forked from OpenOffice are still implemented in Java, which in the end test C++ code making it hard to debug them. LibreOffice has had a long term plan to move them to C++. The project will also focus on fixing the unit tests for errors, if any. I intend to complete this task as my project for GSOC 2023. Once again, it's my great pleasure to work with you on this project. I want to thank all the mentors and admins at LibreOffice to give me this amazing opportunity. Please feel free to contact me if you have any questions or concerns. I look forward to working with you this summer. Thanks and Regards Dipam Turkar
[Libreoffice-bugs] [Bug 155303] New: Asking for a new functionality: to draw or handwrite in Impress or Write
https://bugs.documentfoundation.org/show_bug.cgi?id=155303 Bug ID: 155303 Summary: Asking for a new functionality: to draw or handwrite in Impress or Write Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: puigp...@gmail.com Description: It would be good to be able to have a tab ti draw or handwrite with a digital tablet in Write or Impress, as it is possible in Word and Power Point Actual Results: Now I cannot handwrite on Write or Impress. Expected Results: To have a Tab wuth the tools to handwrite or draw in Impress or Write. Reproducible: Always User Profile Reset: No Additional Info: Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-qa] Live streaming LibreOffice bug triaging (week 20)
I will be live streaming a 1 hour LibreOffice bug triaging session in the Jitsi room https://jitsi.documentfoundation.org/ilmaritriages on Mon, 15 May 2023 at 13:00 UTC Tue, 16 May 2023 at 16:00 UTC Wed, 17 May 2023 at 13:00 UTC Anyone is welcome to interrupt me during the session and ask questions about the process or request me to test something specific. Note: if you want to record the session for your own use, ask me to make you a moderator and then you can click the "meatball menu" in Jitsi's bottom bar and select "Start recording". TDF members can become moderators simply by authenticating (Settings - Profile). Recording only works in Chrome and derivative browsers at the moment. Ilmari
[Libreoffice-bugs] [Bug 155123] XML Form Document: Deleting parts of user defined data type impossible.
https://bugs.documentfoundation.org/show_bug.cgi?id=155123 Julien Nabet changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |serval2...@yahoo.fr |desktop.org | CC||caol...@redhat.com, ||serval2...@yahoo.fr --- Comment #2 from Julien Nabet --- I gave a try with https://gerrit.libreoffice.org/c/core/+/151740. To remove the information with the patch applied, you must select 0 then when clicking on another field, the "0" disappear and let the previous field empty. I would have preferred to be able to remove the content directly but LO retrieves "0" in a way. I must recognize that changing something in extensions is a bit like playing the sorcerer's apprentice for me, hope it won't back fire... Caolán: any thoughts here? I mean, even in forms part of the quoted patch, I wonder if there won't be any wrong side effects somewhere. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154113] Sections: after copy-paste, layout is broken until reload
https://bugs.documentfoundation.org/show_bug.cgi?id=154113 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Status|RESOLVED|VERIFIED --- Comment #6 from BogdanB --- Verified with Version: 7.5.3.2 (X86_64) / LibreOffice Community Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Bad in Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 82873] Image inserted in left-aligned paragraph is centered in text area (see comment #15)
https://bugs.documentfoundation.org/show_bug.cgi?id=82873 --- Comment #18 from Waleed Mortaja --- (In reply to Eyal Rozenberg from comment #15) > Bug reproduction instructions > . > > Actual Results: > > The image is inserted at the center of the text area (and the paragraph text > is placed past it, to the right). Following the new instructions, The image is inserted at the center of the text area but the text remained in its place (to the left of the image). However, with bulleted/numbered lists, the text (plus the number/bullet itself) of the list item does go to the right of the image as in the first image of screenshot added by Yousfu (https://bugs.documentfoundation.org/attachment.cgi?id=104987). Note how the list bullet is to the right of the image of "finished downloading" in the screenshot. Also, when an image has a large width, it gets inserted before the whole list item instead of being part of it. This is shown in the second image of screenshot added by Yousfu. Note how the list bullet is below the image of the video in the screenshot, even though it was pasted in that bullet list and should be inserted after that bullet. I am not sure if "pasted image is inserted at the center (in case of no bulleted/numbered list)" is the same bug as of "pasted image in bulleted/numbered list is inserted before the list item". If not, we may want to submit a separate bug report for one or both of them. What do you think? > Expected Results: > > The image should be aligned to the left boundary of the text area. Correct me if I am wrong, but the expected result would be to have the image to the right of the (LTR) text. which is the right boundary of the text. Right? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95175] Impress: can't change text alignment in text frame of specific ODP via Paragraph (can via Text Anchor or Clear Formatting)
https://bugs.documentfoundation.org/show_bug.cgi?id=95175 --- Comment #15 from BogdanB --- Yes, sorry. Missed some details. I tried with right click - Paragraph: nothing works. Also with toolbar. Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: aa0cbe2c82bbc2295b51357378a68da0d64a44a0 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148422] Assertion failed: (rSData.empty() || rSData[0].m_bRedlineMoved || (rSData[0].m_nRedlineCount == rDoc.getIDocumentRedlineAccess().GetRedlineTable().size())), function Se
https://bugs.documentfoundation.org/show_bug.cgi?id=148422 --- Comment #8 from Telesto --- Repro Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 066b23115c2a360507e306a88da572554daefab7 CPU threads: 8; OS: Mac OS X 12.6.3; UI render: Skia/Raster; VCL: osx Locale: nl-NL (nl_NL.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 155068] Calc: Shortcuts "Ctrl+; " (insert date) and "Ctrl+Shift+; " (insert time) not working
https://bugs.documentfoundation.org/show_bug.cgi?id=155068 --- Comment #9 from bugzi...@rhynas.com --- For me (Mint 21 Ubuntu 22.04 with a UK keyboard), the Date shortcut "Ctrl+;" does work, but the Time shortcut "Ctrl+Shift+;" does not. In fact no user assignment for "Ctrl+Shift+;" works. This affects both Writer and Calc and I think the problem started with LO 7.5.2.2. I'm pretty sure 7.5.1.2 and previous versions were OK. My temporary workaround at present is to assign the Time field to "Ctrl+'". -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103494] [META] Textbox bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103494 BogdanB changed: What|Removed |Added Depends on||129555 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129555 [Bug 129555] Caption of textbox not placed at top of textbox (see c1) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 114426] [META] Caption bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=114426 BogdanB changed: What|Removed |Added Depends on||129555 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=129555 [Bug 129555] Caption of textbox not placed at top of textbox (see c1) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 129555] Caption of textbox not placed at top of textbox (see c1)
https://bugs.documentfoundation.org/show_bug.cgi?id=129555 BogdanB changed: What|Removed |Added CC||buzea.bog...@libreoffice.or ||g Blocks||114426, 103494 --- Comment #7 from BogdanB --- Also in Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community Build ID: aa0cbe2c82bbc2295b51357378a68da0d64a44a0 CPU threads: 16; OS: Linux 5.19; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103494 [Bug 103494] [META] Textbox bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=114426 [Bug 114426] [META] Caption bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
