[Libreoffice-bugs] [Bug 144700] Transparency in ODT page area bitmap fill is not exported to PDF (comment 11)
https://bugs.documentfoundation.org/show_bug.cgi?id=144700 --- Comment #31 from Jambunathan K --- Created attachment 186131 --> https://bugs.documentfoundation.org/attachment.cgi?id=186131&action=edit bug144700-feedback-dtd. March 22, 2023 (LO 7.6 alpha).zip The feedback here is based on Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 4bcf6d9c905e7b5558ee8d9f7f616ce61eadb8f8 CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: en-IN (en_IN); UI: en-US Calc: threaded running on (base) ~$ uname -a Linux debian 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 (2023-01-07) x86_64 GNU/Linux (base) ~$ lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux bookworm/sid Release:n/a Codename: bookworm Contents of `bug144700-feedback-dtd. March 22, 2023 (LO 7.6 alpha).zip` - example-latin-only.odt Same as https://bugs.documentfoundation.org/attachment.cgi?id=175254 (see https://bugs.documentfoundation.org/show_bug.cgi?id=144700#c14) - example-latin-only.pdf - LO version is 7.6.0.0alpha0+.png Version of LO I am using (This is development build less than 6 months old as on Mar 22, 2023) - Birds's eye view of example-latin-only.odt on LO 7.6 alpha.png Not sure if I should see the the two thin black strips (I am not knowledgeable to comment on if the two black strips---I believe they are border pixels---should appear or not. My gut feeling is that the two black strips shouldn't appear.) I will leave the decision to you. - PDF rendering of example-latin-only.od on LO 7.6 alpha.png The PDF rendering matches with what I see in LibreOffice GUI. Good! The "consistentcy" part of my original report is addressed. - bug144700-pay attention to black strips appearing preview image.mp4 Note that "Preview" doesn't show the thin black strips. So there is an incosistency between what the "Preview" window shows and what the LibreOffice compose area shows. This "inconsistency" is a bug. Also note that, as I change the tiling parameters the tiny black strips appear in some cases, and doesn't appear in some cases. There seems to be some inconsistent handling. My gut feeling is that some fine tuning is required. - unzipped This folder contains unzipped version of `example-latin-only.odt`. `Pictures/13AC02C1E6E482E8A2E80086.png' is the background image that gets tiled. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154312] Selection doesn't work correctly if table changes its page
https://bugs.documentfoundation.org/show_bug.cgi?id=154312 --- Comment #2 from Franklin Weng --- The texts are actually selected. Copy and paste could paste all the texts. Just not shown (not highlighted with pale blue background) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154312] Selection doesn't work correctly if table changes its page
https://bugs.documentfoundation.org/show_bug.cgi?id=154312 Franklin Weng changed: What|Removed |Added Version|7.4.4.2 release |3.6.7.2 release Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from Franklin Weng --- Confirmed in 3.6.7.2 (earliest version I installed), probably inherited from OOo. Still reproducible in 7.5.1.2 Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 135239] FIREBIRD migration: Import of a specific table with a combined primary key fails
https://bugs.documentfoundation.org/show_bug.cgi?id=135239 --- Comment #5 from Robert Großkopf --- Bug is still the same with LO 7.5.1.2. Opened the attached database (with experimental features 'on'). Opened the table pane and started migration to Firebird. Table rel_Kasse_Kategorie (Combination of 2 fields for primary key) has not been migrated - error. Tested with LO 7.5.1.2 on OpenSUSE 15.3 64bit rpm Linux. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154320] WestJet's refund policy
https://bugs.documentfoundation.org/show_bug.cgi?id=154320 farecopy changed: What|Removed |Added URL||https://www.farecopy.com/ca ||ncellation/westjet-airlines ||-cancellation-policy-and-re ||fund-fees -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154320] New: WestJet's refund policy
https://bugs.documentfoundation.org/show_bug.cgi?id=154320 Bug ID: 154320 Summary: WestJet's refund policy Product: Impress Remote Version: 1.0.3 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: General Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: davidjhonson...@gmail.com Description: WestJet's refund policy varies depending on the fare type and timing of cancellation. Refunds may be provided for cancellations made within 24 hours of booking, or if WestJet cancels the flight. Refunds are not typically provided for non-refundable fares. Actual Results: WestJet's refund policy Expected Results: WestJet's refund policy Reproducible: Always User Profile Reset: Yes Additional Info: WestJet's refund policy -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 60251] [META] ACCESSIBILITY: Tracking Windows OS accessibility and AT issues
https://bugs.documentfoundation.org/show_bug.cgi?id=60251 Bug 60251 depends on bug 154303, which changed state. Bug 154303 Summary: JAWS no longer announces focused menu item https://bugs.documentfoundation.org/show_bug.cgi?id=154303 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154314] possible memory leak leads to worse and worse application response times if a file is left open for several hours even if the user has done nothing on the computer in t
https://bugs.documentfoundation.org/show_bug.cgi?id=154314 --- Comment #1 from Franklin Weng --- Could you please paste the version info (from Help -> About Libreoffice)? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154315] "Hidden Text" not working correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=154315 --- Comment #1 from Franklin Weng --- Not reproducible in 7.5.1.2: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+xcb) Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW Calc: threaded Select texts with newlines in it and set it to hidden with Format -> Characters -> Font Effects -> Hidden all the newline (I made the paragraph/newline mark shown to observe) are hidden. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154317] Chandigarh call girl
https://bugs.documentfoundation.org/show_bug.cgi?id=154317 Buovjaga changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED Component|Base|deletionRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154319] New: ToC in DOCX has duplicated LS/LE elements; \d in TOC field gives displaced CI and text elements
https://bugs.documentfoundation.org/show_bug.cgi?id=154319
Bug ID: 154319
Summary: ToC in DOCX has duplicated LS/LE elements; \d in TOC
field gives displaced CI and text elements
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Keywords: filter:docx
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: mikekagan...@hotmail.com
Created attachment 186130
--> https://bugs.documentfoundation.org/attachment.cgi?id=186130&action=edit
ToC with \s and \d
The attached DOCX has a table of contents, having this field code:
{ TOC \o "1-3" \h \z \u \s chapter \d ":" }
The \s and \d define that there is the numbering and a specific separator
(colon) before the page number [1].
It results in this ToC text:
1 Ch 11:1
1.1 Subch 1:1
2 Ch 22:1
3 Ch 33:1
Open the attached document in Writer, and inspect the ToC entries. They have
the following structure:
[LS][LS][E#][E][T][#][CI]":" [LE][LE]
Three problems in this structure:
1. [LS] and [LE] (Hyperlink start/end) are duplicated;
2. The colon is enclosed into double quotes, and is followed by a space;
3. [CI] and the colon are displaced, go after [#], while they must precede it.
The resulting text of the ToC (after update) is:
1 Ch 111":"
1.1 Subch 11.1":"
2 Ch 212":"
3 Ch 313":"
Version: 7.5.2.1 (X86_64) / LibreOffice Community
Build ID: e8bf3b441b8370f8440b0339fd9490765a8d57ca
CPU threads: 12; OS: Windows 10.0 Build 19045; UI render: default; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL threaded
[1]
https://support.microsoft.com/en-us/office/field-codes-toc-table-of-contents-field-1f538bc4-60e6-4854-9f64-67754d78d05c
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96272] ODG icon isn't displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=96272 Rizal Muttaqin changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96272] ODG icon isn't displayed
https://bugs.documentfoundation.org/show_bug.cgi?id=96272 Rizal Muttaqin changed: What|Removed |Added CC||riz...@libreoffice.org --- Comment #12 from Rizal Muttaqin --- Not reproducible regardless which icon theme LibreOffice use Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f22d01b7ae96a7efa91c9285f3d2f8c37f05237 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: id-ID (id_ID.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 38305] Symbols in status bar do not follow new Theme in opened document
https://bugs.documentfoundation.org/show_bug.cgi?id=38305 Rizal Muttaqin changed: What|Removed |Added CC||riz...@libreoffice.org --- Comment #14 from Rizal Muttaqin --- Still reproducible with Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f22d01b7ae96a7efa91c9285f3d2f8c37f05237 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: id-ID (id_ID.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96719] UI: Calc icon for "Paste special" + icon "Only numbers" for toolbar
https://bugs.documentfoundation.org/show_bug.cgi?id=96719 Rizal Muttaqin changed: What|Removed |Added CC||riz...@libreoffice.org --- Comment #10 from Rizal Muttaqin --- Current condition: 1. Paste Special has already present in Calc's right click menu regardless any content of the clipboard. Each command also received complete icon. 2. Little arrow for drop-down in Paste command of standard toolbar is content aware of the content of the clipboard, so it just showing what's relevant I don't know which coherence solution to approach, but the paste option in the standard toolbar gives more variant even when I copy one active cell containing the number '1'. Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f22d01b7ae96a7efa91c9285f3d2f8c37f05237 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: id-ID (id_ID.UTF-8); UI: en-US Calc: threaded So what expected actually? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154318] New: Wrong Conditional Formatting 5 Quarters Icon Sets Are Wrong in elementary (SVG) Theme
https://bugs.documentfoundation.org/show_bug.cgi?id=154318 Bug ID: 154318 Summary: Wrong Conditional Formatting 5 Quarters Icon Sets Are Wrong in elementary (SVG) Theme Product: LibreOffice Version: 7.6.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: riz...@libreoffice.org Created attachment 186129 --> https://bugs.documentfoundation.org/attachment.cgi?id=186129&action=edit Expected vs Observed Appearance Steps to Reproduce: 1. Set icon theme to elementary (SVG) --> Tools > Options > LibreOffice > View > Icon Theme 2. Open Calc 3. Access Format > Conditional > Icon Set... 4. Select 5 Quarters All icons has full dark circle while actually it has some white color. Somehow this is affects only elementary SVG variant while elementary bitmap/PNG version does not has the problem Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1f22d01b7ae96a7efa91c9285f3d2f8c37f05237 CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: id-ID (id_ID.UTF-8); UI: en-US Calc: threaded Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 8; OS: Linux 5.19; UI render: default; VCL: kf5 (cairo+xcb) Locale: id-ID (id_ID.UTF-8); UI: en-US Ubuntu package version: 4:7.5.1~rc2-0ubuntu0.22.04.1~lo1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154317] New: Chandigarh call girl
https://bugs.documentfoundation.org/show_bug.cgi?id=154317 Bug ID: 154317 Summary: Chandigarh call girl Product: LibreOffice Version: 3.3.1 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: anjalira...@gmail.com Description: Hey, ladies, I'm waiting to hear from you, Anjali Rana, a hot and sexually attractive Chandigarh call girl, who will be willing to stay all night at your home. I'm extremely knowledgeable on every sex position, and I am an attractive call girl from Chandigarh that you could think of and only. You'll love every minute with me and you will never forget the sexual experiences. https://anjalirana.com/ Actual Results: https://anjalirana.com/ Expected Results: Chandigarh call girl, who will be willing to stay all night at your home. I'm extremely knowledgeable Reproducible: Always User Profile Reset: Yes Additional Info: Chandigarh call girl, who will be willing to stay all night at your home. I'm extremely knowledgeable -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154213] LibeOffice icons on the GNOME desktop are too big
https://bugs.documentfoundation.org/show_bug.cgi?id=154213 Rizal Muttaqin changed: What|Removed |Added CC||qmebic1...@gmail.com, ||riz...@libreoffice.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #4 from Rizal Muttaqin --- @Galdam: As the creator of the icon tought you are interested with this report -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152974] Forms: Borders of text controls switch to 3D if form has been edited in LO 7.5.0.1 and reopened in older versions
https://bugs.documentfoundation.org/show_bug.cgi?id=152974 QA Administrators changed: What|Removed |Added Keywords||bibisectRequest -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 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 154013] download assets should reflect the actual version number
https://bugs.documentfoundation.org/show_bug.cgi?id=154013 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 154041] Missing borders of toolbars ("blended" toolbar w/ work area or other toolbar)
https://bugs.documentfoundation.org/show_bug.cgi?id=154041 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 153989] Autocorrect uses language-specific quotation marks for other languages
https://bugs.documentfoundation.org/show_bug.cgi?id=153989 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 154264] LO Writer freezes while pasting from web and saving document
https://bugs.documentfoundation.org/show_bug.cgi?id=154264 --- Comment #3 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154043] Change object layer via drag&drop is not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=154043 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 154264] LO Writer freezes while pasting from web and saving document
https://bugs.documentfoundation.org/show_bug.cgi?id=154264 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150060] Keyboard Shortcuts for Black and White Screen don't work (Presentation Mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=150060 QA Administrators changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143200] Crash: Assertion failing when pasting a cell to a large-height range
https://bugs.documentfoundation.org/show_bug.cgi?id=143200 QA Administrators changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150060] Keyboard Shortcuts for Black and White Screen don't work (Presentation Mode)
https://bugs.documentfoundation.org/show_bug.cgi?id=150060 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143200] Crash: Assertion failing when pasting a cell to a large-height range
https://bugs.documentfoundation.org/show_bug.cgi?id=143200 --- Comment #8 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150538] Spreadsheet crashes in V. 7.4.0.3 & earlier versions
https://bugs.documentfoundation.org/show_bug.cgi?id=150538 --- Comment #4 from QA Administrators --- Dear Tec, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150538] Spreadsheet crashes in V. 7.4.0.3 & earlier versions
https://bugs.documentfoundation.org/show_bug.cgi?id=150538 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144014] I cannot create a New Style for internet links, without the system Internet Link overriding my style.
https://bugs.documentfoundation.org/show_bug.cgi?id=144014 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144014] I cannot create a New Style for internet links, without the system Internet Link overriding my style.
https://bugs.documentfoundation.org/show_bug.cgi?id=144014 --- Comment #5 from QA Administrators --- Dear nirodhaha, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 142919] Can't open Google Drive documents from nautilus on with Flatpak LibreOffice on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=142919 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148677] Add Avery 5160 to Label Format choices
https://bugs.documentfoundation.org/show_bug.cgi?id=148677 --- Comment #3 from QA Administrators --- Dear MikeH, 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 142919] Can't open Google Drive documents from nautilus on with Flatpak LibreOffice on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=142919 --- Comment #6 from QA Administrators --- Dear Finley Turner-Hall, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 144610] Font drop down does not function correctly throughout the suite
https://bugs.documentfoundation.org/show_bug.cgi?id=144610 --- Comment #3 from QA Administrators --- Dear Brianna Michaela, 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 56164] EDITING: FILEOPEN document shows visible Comment box at wrong place
https://bugs.documentfoundation.org/show_bug.cgi?id=56164 --- Comment #9 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 37152] FILEOPEN Writer mis-shifts OLE object in Microsoft Word .doc
https://bugs.documentfoundation.org/show_bug.cgi?id=37152 --- Comment #11 from QA Administrators --- Dear Christopher M. Penalver, 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 123066] Incorrect Rotate Transition in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=123066 --- Comment #4 from QA Administrators --- Dear Daniel, 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 34619] FILEOPEN DOC Cropped PowerPoint OLE object isn't cropped in Writer (see comment 4)
https://bugs.documentfoundation.org/show_bug.cgi?id=34619 --- Comment #13 from QA Administrators --- Dear sasha.libreoffice, 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 135239] FIREBIRD migration: Import of a specific table with a combined primary key fails
https://bugs.documentfoundation.org/show_bug.cgi?id=135239 --- Comment #4 from QA Administrators --- Dear Robert Großkopf, 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 132061] Page Columns in Notebookbar is not disabled when document is read-only
https://bugs.documentfoundation.org/show_bug.cgi?id=132061 --- Comment #3 from QA Administrators --- Dear Jim Raykowski, 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 129509] Controls in Notebookbar user interfaces don't show as disabled for read-only document.
https://bugs.documentfoundation.org/show_bug.cgi?id=129509 --- Comment #4 from QA Administrators --- Dear Jim Raykowski, 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 107363] Grouped buttons doesn't become properly disabled
https://bugs.documentfoundation.org/show_bug.cgi?id=107363 --- Comment #5 from QA Administrators --- Dear Heiko Tietze, 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 120416] Writer: Copy paste TABLE as Paste special - RTF changes border width from 0, 05 to 0, 75
https://bugs.documentfoundation.org/show_bug.cgi?id=120416 --- Comment #7 from QA Administrators --- Dear Timur, 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 100850] libreoffice base use too much memory
https://bugs.documentfoundation.org/show_bug.cgi?id=100850 --- Comment #18 from QA Administrators --- Dear mug896, 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 131323] Libreoffice pdf conversion fails in FIPS mode
https://bugs.documentfoundation.org/show_bug.cgi?id=131323 --- Comment #16 from michael.ti...@ibm.com --- I was able to run LibreOffice inside a FIPS cluster - using BASH. The error is a complaint that it can't write the PDF file. What should my next step be? Here's the command: work%% cat doit.sh /opt/libreoffice7.3/program/soffice --nologo --norestore --headless --convert-to pdf --outdir . PP4.docx Here's the execution of the command: work%% ./doit.sh Here's the output: convert /var/tmp/PP4.docx -> /var/tmp/PP4.pdf using filter : writer_pdf_Export Error: Please verify input parameters... (SfxBaseModel::impl_store failed: 0xc10(Error Area:Io Class:Write Code:16) /home/buildslave/source/libo-core/sfx2/source/doc/sfxbasemodel.cxx:3202 /home/buildslave/source/libo-core/sfx2/source/doc/sfxbasemodel.cxx:1775) work%% -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154177] libreoffice cannot parse word documents generated by FreeMarker
https://bugs.documentfoundation.org/show_bug.cgi?id=154177 siyi <1749014...@qq.com> changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |1749014...@qq.com |desktop.org | Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED --- Comment #2 from siyi <1749014...@qq.com> --- Created attachment 186128 --> https://bugs.documentfoundation.org/attachment.cgi?id=186128&action=edit The document is typeset incorrectly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 --- Comment #7 from vi...@vincentbentley.co.uk --- Created attachment 186127 --> https://bugs.documentfoundation.org/attachment.cgi?id=186127&action=edit Test image 1280x800 pixels This is a test image of maximum size 1280x800. It shows a 20 pixel thick border in white that surrounds a 1240x760 black rectangle. This image displays perfectly on my 1280x800 screen. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 --- Comment #6 from vi...@vincentbentley.co.uk --- Created attachment 186126 --> https://bugs.documentfoundation.org/attachment.cgi?id=186126&action=edit No display scaling activated As far as I am aware, I am not using any scaling. When enabling fractional scaling at 100% there is no change in my display. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 --- Comment #5 from vi...@vincentbentley.co.uk --- Created attachment 186125 --> https://bugs.documentfoundation.org/attachment.cgi?id=186125&action=edit Info about my Desktop Environment I am using Gnome 42.5 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 --- Comment #4 from vi...@vincentbentley.co.uk --- Created attachment 186124 --> https://bugs.documentfoundation.org/attachment.cgi?id=186124&action=edit Screenshot of customize dialog I took a screenshot of the dialog and the full dialog was copied but the size is 870x819 pixels. The vertical height does not fit on my laptop display. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152173] [MacOS 13] Tooltips bring out-of-focus LO windows to second-to-last position
https://bugs.documentfoundation.org/show_bug.cgi?id=152173 --- Comment #19 from Patrick Luby --- (In reply to Alex Thurgood from comment #18) > Separately confirmed on > > Version: 7.5.1.2 (AARCH64) / LibreOffice Community > Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 > CPU threads: 8; OS: Mac OS X 13.2.1; UI render: Skia/Raster; VCL: osx > Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR > Calc: threaded I use macOS Monterey day-to-day and I could not reproduce this. But on Ventura it is easy to reproduce. Clearly Apple changed something as I don't ever remember inactive applications getting mouse move events. Only mouse drag events were sent in such cases. But sure enough, starting with Ventura, macOS sends mouse move events to LibreOffice. Of course, all of Apple's application work fine with this (surprise, surprise) but these mouse move events confuse the LibreOffice code since every previous release of macOS didn't do this. How to fix this bug? I don't know yet. But it seems to me there might be two separate issues that need to be solved: 1. Tooltips are displayed when the application is unfocused 2. LibreOffice gets pushed up a level in the Z window order I am hoping the second case is triggered by the first case. I'll have to see as I think the tooltip handling code is a layer or two above the native event handler code that I am familiar with. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154316] New: Freeze and crash on autosave
https://bugs.documentfoundation.org/show_bug.cgi?id=154316 Bug ID: 154316 Summary: Freeze and crash on autosave Product: LibreOffice Version: 7.5.1.2 release Hardware: x86-64 (AMD64) OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: takingthem...@gmail.com Description: While typing out a document, at the ten minute mark - LibreOffice attempts to autosave but freezes for 30 seconds and then crashes - with no recovery possible. This has happened three times in a row. Steps to Reproduce: 1.Open LibreOffice to half size screen - Google Docs running in Firefox on other half. 2.Type for ten minutes 3.Crash 4. On Recovery, type recover. 5. Back to last manual save. Actual Results: Back to manual save Expected Results: Autosave and continue Reproducible: Always User Profile Reset: Yes Additional Info: Brand new build - maybe 5 days old? No other programs/problems. Saving to a new file on Desktop using Word Compatible mode. Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: en-GB (en_GB); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131323] Libreoffice pdf conversion fails in FIPS mode
https://bugs.documentfoundation.org/show_bug.cgi?id=131323 --- Comment #15 from michael.ti...@ibm.com --- Timur - We are interested in fixing this issue. Can someone show us where the code is and guide us with the process? I just revalidated the behavior - upload a WORD document to our application which then calls the headless LibreOffice: "message": "Invoking Libre office call with the following command - [libreoffice --nologo --norestore --headless -env:UserInstallation=file:///work_dir/c0379a25-7ef3-43da-849 The only clue so far is : Check exit code - true", We might start running it on the FIPS cluster - but that's still pending. -- Michael Tighe IBM.COM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154045] Upon updating my custon autocorrect completions, user profile becomes corrupt and must be deleted in 7.5.1.2 for any autocorrect features to work even though file valid
https://bugs.documentfoundation.org/show_bug.cgi?id=154045 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report, JoJo. I wasn't able to reproduce with: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Could you please provide: - more precise, simple steps to reproduce the issue, - the version information from Help > About LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 119352] [META] Language issues
https://bugs.documentfoundation.org/show_bug.cgi?id=119352 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||149429 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149429 [Bug 149429] Changing Calc document's language should overwrite cell direct formatting language -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 96000] [META] Spelling and grammar checking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=96000 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||149429 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=149429 [Bug 149429] Changing Calc document's language should overwrite cell direct formatting language -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 149429] Changing Calc document's language should overwrite cell direct formatting language
https://bugs.documentfoundation.org/show_bug.cgi?id=149429 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|AutoCorrection detects |Changing Calc document's |misspelled words in English |language should overwrite |(USA) whether language is |cell direct formatting |English (USA) or None |language Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Keywords||needsUXEval OS|Windows (All) |All CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Blocks||96000, 119352 --- Comment #11 from Stéphane Guillou (stragu) --- I updated the summary to hopefully more accurately describe the issue. Minimal steps from a new document: 1. Open Calc 2. Right-click on cell A1 > Format cell > Font > change language to e.g. French > OK 3. Change language for document to e.g. English (from status bar, or Tools > Language > For all text, or Tools > Options > Language settings > Languages > Default languages for documents) Result: cell A1 is still in French. UX team, what do you think? - Is this difference between Writer and Calc desired? If so, we should probably make it clearer (in UI / in documentation) that direct cell formatting will not be overwritten by a change in default document language. And clarify that the status bar in Calc is to set the "Default language for this document", and not just the selected cells. - Or do we need to make a document language change overwrite the direct cell formatting? Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=96000 [Bug 96000] [META] Spelling and grammar checking bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=119352 [Bug 119352] [META] Language issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154291] I'm editing a doc. then sudenly the pgm freeze, then quit, no saving of the work pending
https://bugs.documentfoundation.org/show_bug.cgi?id=154291 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Please test with a clean profile, Menu/Help/Restart in Safe Mode -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154286] Changing value of date fields fails as MM/DD/YYYY format is not recognized as date after last LibreOffice update
https://bugs.documentfoundation.org/show_bug.cgi?id=154286 --- Comment #10 from pe...@supurovic.net --- D.M.Y;D.M format is what i found out set, and it was coloured red. I was unable to recreate it, but after i added dot and entered D.M.Y;D.M. it was accepted. In my original document all fileds are dates. Thez are used in date calculations, and those calculations break if I edit date filed and try to enter date in MM/DD/ format, which I was forced to do in previous versions and onlz that waz dates worked. Since update calcualtions worked until i tried to edit date fields. It dod not accept MM/DD/ format, but I had to enter dates in DD.MM. format. After I changed D.M.Y;D.M to D.M.Y;M/D/Y I was again able to edit date in MM/DD/ format. That filed that ends up string instead of date is probably because of D.M.Y;D.M. setting. It does not accept MM/DD/ as date so it saves it as string. that is probalbz what happens in already existing date fields. When i edit them and try to keep MM/DD/ which is already entered (and recognized as date) it is converted to string and everything depending on it fails. I usually edit date just to alter year part, but after this update I have to type in whole date in new format to be recognized as date. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154047] Formatting keyboard shortcuts work counter-intuitively
https://bugs.documentfoundation.org/show_bug.cgi?id=154047 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Stéphane Guillou (stragu) --- I don't see that in OOo 3.3 nor in: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Coburn, please provide the information from Help > About LibreOffice, and test in Help > Safe mode to see if the issue persists. Have you actually tested in version 3.3 of LibreOffice? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151756] Menu text almost invisible in Windows 10 dark mode (after sleep or when display connected) (see comment 9)
https://bugs.documentfoundation.org/show_bug.cgi?id=151756 V Stuart Foote changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||4313 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 150915] [META] Windows Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=150915 V Stuart Foote changed: What|Removed |Added Depends on||154313 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154313 [Bug 154313] Writer drop-down menus are colored black -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154313] Writer drop-down menus are colored black
https://bugs.documentfoundation.org/show_bug.cgi?id=154313 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||1756 CC||vsfo...@libreoffice.org Blocks||150915 --- Comment #1 from V Stuart Foote --- Please set "Enable Experimental Features" from Tools -> Options -> Advanced and retest. If that resolves this is a dupe of bug 151756 The os/DE color theme support is more completely implemented in the 7.5 release, experimental in the 7.4 builds. You can also test with with a parallel install of 7.5.1 or nightly master against 7.6, see the Wiki -- https://wiki.documentfoundation.org/Installing_in_parallel Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=150915 [Bug 150915] [META] Windows Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 105948] [META] Undo/Redo bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=105948 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||154048 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=154048 [Bug 154048] Superscripts do not undo properly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154048] Superscripts do not undo properly
https://bugs.documentfoundation.org/show_bug.cgi?id=154048 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Severity|normal |minor Keywords||needsUXEval Blocks||105948 Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Priority|medium |low --- Comment #3 from Stéphane Guillou (stragu) --- I see something different. Using the following steps: 1. write "normal" 2. Ctrl + Shift + P 3. write "super" On the undo stack there is (most recent at the top): - Typing "super" - Apply attributes - Typing "normal" I see two different behaviours depending on the next action: (a) Ctrl + Z removes the superscript string, and continuing writing uses non-superscript characters *even though "Apply attributes" is still on top of the stack* (b) Backspace until all superscript characters are gone, then continuing writing still uses superscript character This not exclusive to superscripts, it is consistent with other formatting options (I tested bold, italic, font colour), but I feel like the two actions (Ctrl + Z vs backspace) are equivalent and should therefore have the same impact. (a) seems particularly odd to me, in that "Apply attributes" is still in the history but new characters don't use the formatting. (I am aware this is the behaviour Coburn would prefer though.) UX/UI team, what do you think? Coburn, do you see something different following my steps? Please also share the info from Help > About LibreOffice. I tested with this version: Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: ru-RU (en_AU.UTF-8); UI: en-US Calc: threaded Same results in 7.0.6.2 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105948 [Bug 105948] [META] Undo/Redo bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154264] LO Writer freezes while pasting from web and saving document
https://bugs.documentfoundation.org/show_bug.cgi?id=154264 --- Comment #2 from Rajasekaran Karunanithi --- It did happened for few times.I just translated few paragraphs of online texts and pasted into LO 7.6 alpha release,then tried to save it.After that it hanged for a while.Then waited for five minutes,nothing happened.So I did end task and then tried 'Document Recovery' but unable to recover the texts. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154314] possible memory leak leads to worse and worse application response times if a file is left open for several hours even if the user has done nothing on the computer in t
https://bugs.documentfoundation.org/show_bug.cgi?id=154314 V Stuart Foote changed: What|Removed |Added OS|All |macOS (All) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154315] New: "Hidden Text" not working correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=154315 Bug ID: 154315 Summary: "Hidden Text" not working correctly Product: LibreOffice Version: 7.3.4.2 release Hardware: x86 (IA32) OS: macOS (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gregory_m_thomp...@yahoo.com Description: When I select multiple text lines to be formatted as hidden text, the CR/LF characters to not get "hidden" so I get the same amount of lines as before but they are apparently blank. Steps to Reproduce: 1.highlight several lines of text in one block to all become "hidden" text. Actual Results: I get what appears to be several blank lines. Expected Results: All the text should be collapsed as if it wasn't there at all. Reproducible: Always User Profile Reset: No Additional Info: see "Expected Results" -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 133089] macOS: Some character can't be rendered; square
https://bugs.documentfoundation.org/show_bug.cgi?id=133089 --- Comment #5 from bunkem --- Created attachment 186123 --> https://bugs.documentfoundation.org/attachment.cgi?id=186123&action=edit Screen shot of missing characters in style list on Mac -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154314] New: possible memory leak leads to worse and worse application response times if a file is left open for several hours even if the user has done nothing on the computer
https://bugs.documentfoundation.org/show_bug.cgi?id=154314 Bug ID: 154314 Summary: possible memory leak leads to worse and worse application response times if a file is left open for several hours even if the user has done nothing on the computer in that time. Product: LibreOffice Version: 7.3.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: gregory_m_thomp...@yahoo.com Description: I think there may be a memory leak since Libre Office writer gets stuck on the spinning wheel (even if I am NOT trying to save) if a text file is open for a long time. If I quit Libre Office every two hours or so, I don't get that problem. Steps to Reproduce: 1. open a document in Writer on the MacBook Air w MacOS v13.2.1 and leave open for a few hours. 2. Gets progressively less responsive. Actual Results: It may be a minute or more that the wheel spins and I have not performed ANY user activity on the Mac. Expected Results: Libre Office was as responsive as expected after restartiing it. Reproducible: Always User Profile Reset: No Additional Info: Restarting Libre Office fixes the problem. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108800] [META] Print related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=108800 Bug 108800 depends on bug 113765, which changed state. Bug 113765 Summary: PRINT Partial objects are printed on other pages https://bugs.documentfoundation.org/show_bug.cgi?id=113765 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108741] [META] Shapes bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108741 Bug 108741 depends on bug 113765, which changed state. Bug 113765 Summary: PRINT Partial objects are printed on other pages https://bugs.documentfoundation.org/show_bug.cgi?id=113765 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113765] PRINT Partial objects are printed on other pages
https://bugs.documentfoundation.org/show_bug.cgi?id=113765 Dieter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #9 from Dieter --- Bug no longer present in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 140683] Shift of view, after export of the document to xml (Writer)
https://bugs.documentfoundation.org/show_bug.cgi?id=140683 Dieter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #5 from Dieter --- Bug has gone in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded => RESOLVED WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 116864] The table cell selection changes after undo of a drag & drop change
https://bugs.documentfoundation.org/show_bug.cgi?id=116864 --- Comment #7 from Dieter --- Still present in Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 124114] FILEOPEN DOCX: View setting changes from "Web" to "Normal"
https://bugs.documentfoundation.org/show_bug.cgi?id=124114 --- Comment #10 from Dieter --- Same behaviour in Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded But my question to Jan Holesovsky is still open. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154313] New: Writer drop-down menus are colored black
https://bugs.documentfoundation.org/show_bug.cgi?id=154313 Bug ID: 154313 Summary: Writer drop-down menus are colored black 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: soli...@gmail.com Created attachment 186122 --> https://bugs.documentfoundation.org/attachment.cgi?id=186122&action=edit File with an image where you can see the bug At the beginning everything works fine. But at some point and without my being able to appreciate when, the drop-down menus are colored black and the texts are not distinguishable, which remain in their black color. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153988] Autocorrect dialog should offer starting-ending quote pairs more conveniently
https://bugs.documentfoundation.org/show_bug.cgi?id=153988 Dieter changed: What|Removed |Added Keywords||needsUXEval CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153987] Can't set per-language quotation marks in Tools | AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=153987 Dieter changed: What|Removed |Added Whiteboard| QA:needsComment| CC||dgp-m...@gmx.de, ||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval --- Comment #1 from Dieter --- Language selection is greyed out in the following tabs: Options | Localised Options | Word Completion. You can change language selection in the following tabs: Replace | Exceptions. I couldn't find any information in LO help. I don't see a reason for this and so I would call it a bug. But let's ask design-team. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 113944] [META] Options dialog's Writer settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113944 Dieter changed: What|Removed |Added Depends on||153932 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153932 [Bug 153932] OPTIONS DIALOG: Settings in Mail Merge Email dialog doesn't work -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 102998] [META] Mail merge bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=102998 Dieter changed: What|Removed |Added Depends on||153932 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=153932 [Bug 153932] OPTIONS DIALOG: Settings in Mail Merge Email dialog doesn't work -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153932] OPTIONS DIALOG: Settings in Mail Merge Email dialog doesn't work
https://bugs.documentfoundation.org/show_bug.cgi?id=153932 Dieter changed: What|Removed |Added Hardware|x86-64 (AMD64) |All Summary|With serial e-mail |OPTIONS DIALOG: Settings in |LibreOffice 7.5.1 will not |Mail Merge Email dialog |connect to the server |doesn't work CC||dgp-m...@gmx.de Whiteboard| QA:needsComment| OS|Linux (All) |All Status|UNCONFIRMED |NEW Blocks||113944, 102998 Ever confirmed|0 |1 --- Comment #1 from Dieter --- Yes, doesn't work Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (de_DE); UI: en-GB Calc: CL threaded Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102998 [Bug 102998] [META] Mail merge bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=113944 [Bug 113944] [META] Options dialog's Writer settings bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154286] Changing value of date fields fails as MM/DD/YYYY format is not recognized as date after last LibreOffice update
https://bugs.documentfoundation.org/show_bug.cgi?id=154286 ady changed: What|Removed |Added CC||mikekagan...@hotmail.com Status|NEEDINFO|NEW --- Comment #9 from ady --- In a hunch, I am CC'ing Mike Kaganski. Maybe he happens to know what's going on, but even if he doesn't, maybe he will be able to point to someone who might. (In reply to pedja from comment #8) > I uploaded example, but I think it is not the same as after i updated Date > acceptance pattern, I amunable to set it back as it was. > > It was D.M.Y;D.M but that is not accepted. I entered D.M.Y;D.M. to make > example. This is what seems to be wrong. For example, when the Locale is English (USA), the default Date acceptance pattern is "M/D/Y;M/D". I am not seeing the reason for Calc to flag "D.M.Y;D.M." as wrong with a red color except maybe the very last dot after the last "M". But even if that's the problem, why now and not before? > > The first row is entered as MM/DD/ > The second row is entered as DD.MM. In attachment 186121 from comment 7, cell A1 (that was supposed to be MM/DD/ according to your comment 8) is not really a date but text – tricky, I know. This seems to match the Date acceptance pattern of "D.M.Y;D.M." (with or without the latest dot/period/stop) which doesn't include MM/DD/ (for this example, according to your comment 8). Using my settings, I see that cell A1 starts with an apostrophe. I'm not sure that you are seeing it under your Locale settings, or that you introduced it intentionally; probably not. This reminds me of another very tricky and unclear bug report involving dates and apostrophe (not seen by the original reporter) and Date acceptance pattern too: https://bugs.documentfoundation.org/show_bug.cgi?id=148747#c39 – just in case anyone is interested, I would suggest only reading after c#35 and not before it, because it could be more confusing than anything else. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153201] Frequent and random crashes whilst editing cells and other actions.
https://bugs.documentfoundation.org/show_bug.cgi?id=153201 eisa01 changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #8 from eisa01 --- Thanks, I'll then close this as WFM -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154310] Exporting cell areas with Ctrl-C does not respect conditional formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=154310 --- Comment #7 from Gerhard Schmidt --- I added the conditional and did not rename the "unbenannt1", because I do not need this template any further. brgs, gsc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154312] New: Selection doesn't work correctly if table changes its page
https://bugs.documentfoundation.org/show_bug.cgi?id=154312 Bug ID: 154312 Summary: Selection doesn't work correctly if table changes its page Product: LibreOffice Version: 7.4.4.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kuraga...@mail.ru CC: kuraga...@mail.ru 1. Create a table - 4 rows, 2 columns. 2. Join the rows of the first column. 3. Write at the first column, first row: "A B C D". 4. Result: -- | A | | |- | B | | |- | C | | |- | D | | -- 5. Move the table at the end of the page: -- | A | | |- | B | | |- < New Page > | C | | |- | D | | -- 6. Move the cursor at "A". 7. Press -. "A" will be selected. 8. Press -. "B" will be selected. 9. Press -. "C" *will not* (visually) be selected. 10. Press -. "D" *will not* (visually) be selected. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154310] Exporting cell areas with Ctrl-C does not respect conditional formatting
https://bugs.documentfoundation.org/show_bug.cgi?id=154310 --- Comment #6 from Gerhard Schmidt --- I tested a conditional formatting under Linux with LibreOffice in version 7.3.3.1. This shows the same behaviour, but there all conditions are false (instead of true like in the Windows case). brgs, gsc -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154303] JAWS no longer announces focused menu item
https://bugs.documentfoundation.org/show_bug.cgi?id=154303 Michael Weghorn changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de |desktop.org | Status|NEW |ASSIGNED --- Comment #2 from Michael Weghorn --- Pending fix: https://gerrit.libreoffice.org/c/core/+/149255 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154286] Changing value of date fields fails as MM/DD/YYYY format is not recognized as date after last LibreOffice update
https://bugs.documentfoundation.org/show_bug.cgi?id=154286 --- Comment #8 from pe...@supurovic.net --- (In reply to ady from comment #6) > * Are these documents ods? Or instead, are we talking about some other > format such as xls/xlsx? Yes, ODS. > * Any chance you could attach a sample document that is/was failing for you > (after deleting any private/confidential info)? I uploaded example, but I think it is not the same as after i updated Date acceptance pattern, I amunable to set it back as it was. It was D.M.Y;D.M but that is not accepted. I entered D.M.Y;D.M. to make example. The first row is entered as MM/DD/ The second row is entered as DD.MM. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 --- Comment #3 from V Stuart Foote --- I resized display to 1280px x 800px at os/DE 100% scaling. The Customize dialog appears at the same 650px x 613px and simply takes up more of the display, but all controls still fit as is expected as our minimum y-size is 768px. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154286] Changing value of date fields fails as MM/DD/YYYY format is not recognized as date after last LibreOffice update
https://bugs.documentfoundation.org/show_bug.cgi?id=154286 --- Comment #7 from pe...@supurovic.net --- Created attachment 186121 --> https://bugs.documentfoundation.org/attachment.cgi?id=186121&action=edit DATE test -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 147718] LO(7.2) XML Form Document cannot unlock Read-only / Write-protected via any visible UI option
https://bugs.documentfoundation.org/show_bug.cgi?id=147718 Robert Großkopf changed: What|Removed |Added CC||rob...@familiegrosskopf.de --- Comment #15 from Robert Großkopf --- Don't know why this one has been set to NEW. I have downloaded first attachment, set the form in Design-Mode (Form → Design-Mode | also available in Form Control bar) and could delete or change controls as I want. A form will be opened for input data, if it is opened again after first form design. So you have to switch to Design Mode. Writer isn't available for set any option if I only open a XML Form Document. I have to open a Writer document to set options here. So this option should have nothing to do with XML Form Document. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from V Stuart Foote --- On a 96 dpi display 1920 x 1200 with os/DE scaling the Customize dialog measures 650px x 613px -- it will fit just fine on a 1024px x 768px display which is our minimum. When users "scale" their UI to other than 100% that is when dialogs and other UI elements can "appear" oversize. IMHO => NOB For OP please describe your os/DE scaling? =-testing-= Version: 7.5.1.2 (X86_64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: b5c3a7502f7ff6ccf0f829c1f3a2ba50b8584c41 CPU threads: 8; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154021] Customize dialog is too big to display on 1280x800 laptop screen
https://bugs.documentfoundation.org/show_bug.cgi?id=154021 Thomas Lendo changed: What|Removed |Added CC||thomas.le...@gmail.com --- Comment #1 from Thomas Lendo --- >From what display resolution is LibreOffice designed? If that's 1280x800 or smaller, then this buh should be corrected. -- You are receiving this mail because: You are the assignee for the bug.
