[Libreoffice-bugs] [Bug 157157] Underscores in MathType equations in a .DOCX file do not convert correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=157157 BogdanB changed: What|Removed |Added Summary|Underscores in MathType |Underscores in MathType |equations in a .docs file |equations in a .DOCX file |do not convert correctly|do not convert correctly -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157157] Underscores in MathType equations in a .docs file do not convert correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=157157 BogdanB changed: What|Removed |Added Product|Document Liberation Project |LibreOffice Component|General |Writer CC||buzea.bog...@libreoffice.or ||g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108990] [META] HTML paste special bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108990 raal changed: What|Removed |Added Depends on||157073 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157073 [Bug 157073] Simple HTML elements for FORMATTING () are ignored on Paste -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157073] Simple HTML elements for FORMATTING () are ignored on Paste
https://bugs.documentfoundation.org/show_bug.cgi?id=157073 raal changed: What|Removed |Added Version|7.6.0.3 release |4.1.0.4 release Ever confirmed|0 |1 Blocks||108990 Status|UNCONFIRMED |NEW CC||r...@post.cz --- Comment #1 from raal --- test page https://www.w3schools.com/tags/tryit.asp?filename=tryhtml_sup Reproducible with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8dbf35c48698e49c527d740853ce4edc4f1afa9 CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded and Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108990 [Bug 108990] [META] HTML paste special bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157165] New: "target already exists" randomly appears trying to open files on mounted SSHFS drive
https://bugs.documentfoundation.org/show_bug.cgi?id=157165 Bug ID: 157165 Summary: "target already exists" randomly appears trying to open files on mounted SSHFS drive Product: LibreOffice Version: 7.5.5.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lo...@psychoros.com Description: I have several Calc files stored on a local server that is mounted via SSHFS on the Arch Linux machine that runs Calc (7.5.5). Calc is usually already loaded and minimized. Doesn't seem to matter if I expand it and click a "recent document" icon or use a menu. Often the files just open normally like any other file. But randomly (at least I can't see a pattern) I get a small dialog saying "target already exists" with the only option being "OK". The colorful wait cursor continues to spin for maybe a minute, but nothing else happens. Sometimes an immediate retry will work properly, sometimes another selection method seems to be required. Once the file is open, all other actions including save and close work normally. FILEOPEN Steps to Reproduce: 1.The only sure condition is the files are on an SSHFS drive 2.Maybe Arch Linux... 3.Try any way to open a file... Many times... Actual Results: Randomness... Expected Results: Would love to hear any clues about what might be triggering the failures to open! Once I get the file open it works great, and often the files even open immediately. Does the message give any clues? Reproducible: Sometimes User Profile Reset: No Additional Info: Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 8; OS: Linux 6.4; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US 7.5.5-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157144] FILEOPEN DOCX Tracked changes disappeared
https://bugs.documentfoundation.org/show_bug.cgi?id=157144 raal changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||r...@post.cz --- Comment #1 from raal --- I can confirm with Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d8dbf35c48698e49c527d740853ce4edc4f1afa9 CPU threads: 4; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157164] Frame Vertical Posn preview does not look like documentation says
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 --- Comment #3 from Jim Avera --- That wasn't quite right. The docs say: "The green rectangle represents the selected object and the red rectangle represents the alignment reference point. If you anchor the object as a character, the reference rectangle changes to a red line." Actual behavior: Nothing is shown in red. There is a grey box floating in the middle which I don't understand, and there is a green rectangle which moves when you adjust the Vertical Position offset. There is no display of where the reference baseline is. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157164] Frame Vertical Posn preview does not look like documentation says
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 Jim Avera changed: What|Removed |Added Summary|Red baseline not shown in |Frame Vertical Posn preview |Vertical Position preview |does not look like |with "as character" |documentation says |(frames)| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97511] Handling of Q_MOD1 +Q in menus -- not functional from OOo
https://bugs.documentfoundation.org/show_bug.cgi?id=97511 --- Comment #15 from V Stuart Foote --- Handling of the Q_MOD1 (+Q) shortcut remains defective with STR as in OP and comment 2, can not use shortcut to quit from LibreOffice when in the main menu. While O_MOD1 +O shortcut works. =-testing-= Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d88779fc86385dde1215fd28b78a69eacc6b4f97 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157156] Symbols in a MathType equation do not convert correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=157156 Telesto changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Telesto --- Confirm Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: e60ef8651cfb30335471d1622e58c13eebc7d58b CPU threads: 8; OS: Mac OS X 13.4.1; UI render: default; 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 157164] Red baseline not shown in Vertical Position preview with "as character" (frames)
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 --- Comment #2 from Jim Avera --- Created attachment 189456 --> https://bugs.documentfoundation.org/attachment.cgi?id=189456=edit screenshot -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157164] Red baseline not shown in Vertical Position preview with "as character" (frames)
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 --- Comment #1 from Jim Avera --- Created attachment 189455 --> https://bugs.documentfoundation.org/attachment.cgi?id=189455=edit noredline.odt demo document -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157164] New: Red baseline not shown in Vertical Position preview with "as character" (frames)
https://bugs.documentfoundation.org/show_bug.cgi?id=157164 Bug ID: 157164 Summary: Red baseline not shown in Vertical Position preview with "as character" (frames) Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jim.av...@gmail.com Description: See the last paragraph in docs at https://help.libreoffice.org/latest/en-US/text/swriter/01/05060100.html The frame properties "Vertical Position" preview should (the doc says) display a red line showing the reference point when anchored "as character". I'm guesing this line should be at the baseline of the sample text, since the baseline is the reference point when anchored "as character". However there's no red line, but the green rectangle which applies to other kinds of anchors (other than "as character"). Steps to Reproduce: 1. Open attached "noredline.odt" 2. Select the frame; rightclick-Properties Actual Results: The preview shows a green rectangle even though Anchor is "As character" Expected Results: Should agree with the documentation (if the code is correct, please update docs) Reproducible: Always User Profile Reset: No Additional Info: The behavior is 7.5.5.2 is the same as in 24.2alpha (master) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157156] Symbols in a MathType equation do not convert correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=157156 Telesto changed: What|Removed |Added Component|Formula Editor |Writer -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157156] Symbols in a MathType equation do not convert correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=157156 Telesto changed: What|Removed |Added Component|General |Formula Editor Product|Document Liberation Project |LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143167] Calc "Freeze Rows and Columns" randomly forgets row and column settings even though feature still checked on
https://bugs.documentfoundation.org/show_bug.cgi?id=143167 --- Comment #14 from Ron --- (In reply to Buovjaga from comment #10) > (In reply to pierre_aussaguel from comment #2) > > 1.a : move the LibreOffice windows to the other screnn. The freeze is lost. > > It is still checked in the menu. > > > > or > > > > 1.b : activate the lateral bar (by pressing F11 for exemple). The freeze is > > also lost. > > Ron: do you reproduce the issue using these ways (lateral bar meaning > Sidebar)? Hello Buovjaga, I do not have another screen to move the Calc windows to, so cannot determine that question. Activating the lateral bar by pressing F11 does NOT lose the freeze. The freeze is lost only when I save the file and reopen it later. I see that Libre Office is at Version 7.6 now. Has this bug been fixed yet? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157158] [UI] Comment arrow drop down is white/light grey when in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=157158 Telesto changed: What|Removed |Added Keywords||bibisectRequest CC||tele...@surfxs.nl -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157160] [CRASH] New "Search" field in Options dialog crashes all the time
https://bugs.documentfoundation.org/show_bug.cgi?id=157160 V Stuart Foote changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||vsfo...@libreoffice.org Ever confirmed|0 |1 --- Comment #1 from V Stuart Foote --- Confirmed, but just the Options dialog closes without result. No hang and LO continues to run. =-testing-= Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d88779fc86385dde1215fd28b78a69eacc6b4f97 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157154] Permanent changing Paragraph Style Dropdown in LO 7.6 is unusable and a WCAG violation
https://bugs.documentfoundation.org/show_bug.cgi?id=157154 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||2666 --- Comment #2 from V Stuart Foote --- See bug 152666 for rational and use case. The drop list is finite, and responds to template handling for new documents allowing customization on new document creation. The Sidebar Style deck 'Stylist' provides fully functional style based manipulation. The WCAG aspect is not valid as the handling of styles *is* consistent, just that that drop list defaults and 'Applied' style handling has evolved to be more in line with Sidebar 'Style' deck's content panels. IMHO => NAB and Invalid -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156916] Signature line uses dark icon with dark theme (KDE Plasma)
https://bugs.documentfoundation.org/show_bug.cgi?id=156916 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 153831] dysfunctional animations in Impress
https://bugs.documentfoundation.org/show_bug.cgi?id=153831 --- Comment #2 from QA Administrators --- Dear Palongo, 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 154142] Crash in: SfxUndoManager::SetMaxUndoActionCount(unsigned __int64)
https://bugs.documentfoundation.org/show_bug.cgi?id=154142 --- Comment #2 from QA Administrators --- Dear gordsown, 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 156907] Writer on Mac confuses users when opening a document from a readonly location.
https://bugs.documentfoundation.org/show_bug.cgi?id=156907 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 156872] Request for formatting Calc spreads in ics
https://bugs.documentfoundation.org/show_bug.cgi?id=156872 QA Administrators changed: What|Removed |Added Whiteboard|Export Calc doc to ics |Export Calc doc to ics |format |format QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 153826] PROBLEM W/ CREATED FIELD
https://bugs.documentfoundation.org/show_bug.cgi?id=153826 --- Comment #2 from QA Administrators --- Dear ROD DAVIS, 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 153815] Removing table jumps to start of document
https://bugs.documentfoundation.org/show_bug.cgi?id=153815 --- Comment #3 from QA Administrators --- Dear Marcin Juszkiewicz, 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 153601] Crash when saving a document with gpg-key encryption ( EXCEPTION_ACCESS_VIOLATION_READ )
https://bugs.documentfoundation.org/show_bug.cgi?id=153601 --- Comment #10 from QA Administrators --- Dear subzero, 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 153018] The entire document loses formatting done when I use the clone formatting tool
https://bugs.documentfoundation.org/show_bug.cgi?id=153018 --- Comment #2 from QA Administrators --- Dear Jose Carrasco, 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 153371] Spelling tool causes crash and ANR message on windows 11 and high CPU usage
https://bugs.documentfoundation.org/show_bug.cgi?id=153371 --- Comment #4 from QA Administrators --- Dear CharlieRamirez, 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 152438] Improvement needed in LibreOffice submenu
https://bugs.documentfoundation.org/show_bug.cgi?id=152438 --- Comment #5 from QA Administrators --- Dear emaildimariorossi, 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 152409] ^ not working randomly with spanish keyboard
https://bugs.documentfoundation.org/show_bug.cgi?id=152409 --- Comment #6 from QA Administrators --- Dear Robert Estalella, 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 152273] Crash in: SwCursor::UpDown(bool, unsigned short, Point const *, __int64, SwRootFrame &)
https://bugs.documentfoundation.org/show_bug.cgi?id=152273 --- Comment #8 from QA Administrators --- Dear Loretta, 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 97511] Handling of Q_MOD1 +Q in menus -- not functional from OOo
https://bugs.documentfoundation.org/show_bug.cgi?id=97511 --- Comment #14 from QA Administrators --- Dear V Stuart Foote, 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 89385] Edit mode is password is not working on DOC files
https://bugs.documentfoundation.org/show_bug.cgi?id=89385 --- Comment #10 from QA Administrators --- Dear Zeki Bildirici, 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 78583] Cannot select (move, resize) floating frame
https://bugs.documentfoundation.org/show_bug.cgi?id=78583 --- Comment #11 from QA Administrators --- Dear Ulrich Windl, 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 74374] UI: 'marching ants' doesn't stay with copied cells when rows are inserted
https://bugs.documentfoundation.org/show_bug.cgi?id=74374 --- Comment #7 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 74373] UI: Slightly increased Xorg CPU usage with 'marching ants' on hidden Calc window
https://bugs.documentfoundation.org/show_bug.cgi?id=74373 --- Comment #8 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 72687] poor precision in rotation (Draw)
https://bugs.documentfoundation.org/show_bug.cgi?id=72687 --- Comment #19 from QA Administrators --- Dear Roberto Casini, 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 139536] [XSLX] Conditional Formatting is lost on import
https://bugs.documentfoundation.org/show_bug.cgi?id=139536 --- Comment #8 from QA Administrators --- Dear Dennis Roczek, 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 128331] Horizontal snap to grid is broken under zoom value 120%
https://bugs.documentfoundation.org/show_bug.cgi?id=128331 --- Comment #5 from QA Administrators --- Dear medmedin2014, 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 127972] Comments don't refresh on field shading on/off
https://bugs.documentfoundation.org/show_bug.cgi?id=127972 --- Comment #8 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 120755] FILEOPEN DOC: Grouped, Linked Textbox saved by MSO not imported
https://bugs.documentfoundation.org/show_bug.cgi?id=120755 --- Comment #5 from QA Administrators --- Dear Luke, 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 119240] Accessing files on CIFS Share when multiple shares are mounted simultaneously
https://bugs.documentfoundation.org/show_bug.cgi?id=119240 --- Comment #6 from QA Administrators --- Dear ulrich.kiefer, 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 118921] FILESAVE to .xlsm files with password protection not working (Calc)
https://bugs.documentfoundation.org/show_bug.cgi?id=118921 --- Comment #5 from QA Administrators --- Dear kam3don, 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 113973] Linux middle mouse button copy does not work correctly
https://bugs.documentfoundation.org/show_bug.cgi?id=113973 --- Comment #38 from QA Administrators --- Dear Michael Lashkevich, 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 157163] NotebookBar tabs' background color does not extend to the right, "looks" broken with a wide window
https://bugs.documentfoundation.org/show_bug.cgi?id=157163 V Stuart Foote changed: What|Removed |Added CC||vsfo...@libreoffice.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from V Stuart Foote --- Are you using a Personalization theme? Some similarity when the Personalization 'White' preinstalled theme while using the Light os/DE mode instead of the default look without theme. Otherwise can not confirm an issue for Windows builds with defaults and Personalization not in use. =-testing-= Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d88779fc86385dde1215fd28b78a69eacc6b4f97 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157124] Frame Vertical Position Top/Bottom Reversed in Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=157124 Jim Avera changed: What|Removed |Added Attachment #189392|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157124] Frame Vertical Position Top/Bottom Reversed in Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=157124 Jim Avera changed: What|Removed |Added Attachment #189393|0 |1 is obsolete|| -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157124] Frame Vertical Position Top/Bottom Reversed in Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=157124 --- Comment #6 from Jim Avera --- Created attachment 189454 --> https://bugs.documentfoundation.org/attachment.cgi?id=189454=edit newdemo.png (screenshot) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157124] Frame Vertical Position Top/Bottom Reversed in Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=157124 --- Comment #5 from Jim Avera --- Created attachment 189453 --> https://bugs.documentfoundation.org/attachment.cgi?id=189453=edit newdemo.odt -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157124] Frame Vertical Position Top/Bottom Reversed in Properties
https://bugs.documentfoundation.org/show_bug.cgi?id=157124 --- Comment #4 from Jim Avera --- I'm attaching a new demo and screenshot which shows all three settings: "Bottom to Baseline" "Center to Baseline" "Top to Baseline" and it is clear that "Top" and "Bottom" are reversed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156872] Request for formatting Calc spreads in ics
https://bugs.documentfoundation.org/show_bug.cgi?id=156872 8023...@pm.me changed: What|Removed |Added Version|unspecified |3.3 all versions Whiteboard|Export Calc doc to ics |Export Calc doc to ics |format QA:needsComment |format -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157153] No subpixel smoothing in LO 7.6 (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157153 --- Comment #7 from anixx...@gmail.com --- Created attachment 189452 --> https://bugs.documentfoundation.org/attachment.cgi?id=189452=edit Scale: 50%. Skia is off. Text on sheet is barely readable due to greyscale smoothing. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157153] No subpixel smoothing in LO 7.6 (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157153 --- Comment #6 from anixx...@gmail.com --- Created attachment 189451 --> https://bugs.documentfoundation.org/attachment.cgi?id=189451=edit Skia is on. Dialog. Skia is on. Font in dialog is greyscale-only, absolutely awful. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157153] No subpixel smoothing in LO 7.6 (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157153 --- Comment #5 from anixx...@gmail.com --- Created attachment 189450 --> https://bugs.documentfoundation.org/attachment.cgi?id=189450=edit Skia is on. Font on sheet is OK, but font in menu is smeared Skia is on. Font on sheet is OK, but font in menu is smeared. Font in input fields and line numbers is greyscale-only. The buttons have visual defects (dots in right-bottom corner). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157163] NotebookBar tabs' background color does not extend to the right, "looks" broken with a wide window
https://bugs.documentfoundation.org/show_bug.cgi?id=157163 --- Comment #1 from Jeff Fortin Tam --- Created attachment 189449 --> https://bugs.documentfoundation.org/attachment.cgi?id=189449=edit Screenshot Pictured: LibreOffice writer (above) vs Firefox 117 (bottom-left) and the standard GTK4-demo application (bottom-right). Matching the GTK look would be ideal. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Jeff Fortin Tam changed: What|Removed |Added Depends on||157163 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157163 [Bug 157163] NotebookBar tabs' background color does not extend to the right, "looks" broken with a wide window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107191] [META] Notebookbar theming issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107191 Jeff Fortin Tam changed: What|Removed |Added Depends on||157163 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157163 [Bug 157163] NotebookBar tabs' background color does not extend to the right, "looks" broken with a wide window -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157163] NotebookBar tabs' background color does not extend to the right, "looks" broken with a wide window
https://bugs.documentfoundation.org/show_bug.cgi?id=157163 Jeff Fortin Tam changed: What|Removed |Added Blocks||107191, 107237 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107191 [Bug 107191] [META] Notebookbar theming issues https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157153] No subpixel smoothing in LO 7.6 (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157153 --- Comment #4 from anixx...@gmail.com --- Created attachment 189448 --> https://bugs.documentfoundation.org/attachment.cgi?id=189448=edit Dialog. Skia is off, font is good -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157163] New: NotebookBar tabs' background color does not extend to the right, "looks" broken with a wide window
https://bugs.documentfoundation.org/show_bug.cgi?id=157163 Bug ID: 157163 Summary: NotebookBar tabs' background color does not extend to the right, "looks" broken with a wide window Product: LibreOffice Version: 7.4.0.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: nekoh...@gmail.com Description: This is cosmetic, but fairly annoying, particularly in the light theme variant of the GTK3 version (a bit less noticeable in the dark version): the tab widgets have a dark gray background, but this background does not extend to the right like normal GTK applications (or even other non-native apps like Firefox). Please see the attached screenshot. Steps to Reproduce: 1. Launch LibreOffice on a high-resolution, very wide-screen monitor, in light mode. Actual Results: Tabs widgets background is not extended. Expected Results: Tabs widgets background should fill the empty space. Reproducible: Always User Profile Reset: No Additional Info: -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157153] No subpixel smoothing in LO 7.6 (regression)
https://bugs.documentfoundation.org/show_bug.cgi?id=157153 --- Comment #3 from anixx...@gmail.com --- Created attachment 189447 --> https://bugs.documentfoundation.org/attachment.cgi?id=189447=edit Skia is off, sheet smoothing is greyscale only. Skia is off, sheet smoothing is greyscale only. Font:Tahoma. Interface font is perfect. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157149] Carppy green pictures on macOS Catalina
https://bugs.documentfoundation.org/show_bug.cgi?id=157149 --- Comment #9 from CTAC --- soffice --calc opens Calc!!! but extremely slow, minutes to launch and no any green garbage on the screen with this way of launch even without SAL_SKIA=raster -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127972] Comments don't refresh on field shading on/off
https://bugs.documentfoundation.org/show_bug.cgi?id=127972 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #7 from Aaron --- This bug is still present in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157159] Text in comments has a white highlight
https://bugs.documentfoundation.org/show_bug.cgi?id=157159 Aaron changed: What|Removed |Added CC||aaronth...@gmail.com --- Comment #2 from Aaron --- Thank you for reporting the bug. I can not reproduce the bug in Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: ca8fe7424262805f223b9a2334bc7181abbcbf5e CPU threads: 4; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-AU (fr_FR); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156862] Copy anything from an application doesn't past onto Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=156862 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #4 from Stéphane Guillou (stragu) --- Do you use a clipboard manager? If that's the case, does deactivating it change anything? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156898] F1 on Anchor menu does not open right Help page
https://bugs.documentfoundation.org/show_bug.cgi?id=156898 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Stéphane Guillou (stragu) --- Repro with gen VCL plugin in: Version: 7.6.1.1 (X86_64) / LibreOffice Community Build ID: c7cda394c5de06de37d8109c310df89a4d4c3a98 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: x11 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 81636] Not possible to view two formulas at the same time in different Calc instances
https://bugs.documentfoundation.org/show_bug.cgi?id=81636 --- Comment #26 from m.a.riosv --- (In reply to DErik from comment #25) > ... https://www.libreoffice.org/community/developers/ https://www.libreoffice.org/about-us/who-are-we/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157158] [UI] Comment arrow drop down is white/light grey when in dark mode
https://bugs.documentfoundation.org/show_bug.cgi?id=157158 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Keywords||regression --- Comment #2 from m.a.riosv --- Reproducible Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: beaea2e992912b4747d790070b26371f557b1f57 CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Jumbo seems regression form Version: 7.5.7.0.0+ (X86_64) / LibreOffice Community Build ID: b00ebfb4f0803ef276f452e17d9e99f2229ef32f CPU threads: 16; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156913] libreoffice-qt5 bug: unwanted line advance after deadkey (in libreoffice writer)
https://bugs.documentfoundation.org/show_bug.cgi?id=156913 --- Comment #3 from Zophonías Jónsson --- (In reply to Stéphane Guillou (stragu) from comment #2) It may not be worth spending much time on this. After upgrade to OpenSuse Leap 15.5 which downgrades LibreOffice to 7.5.4.1 this problem is fixed. I can also not reproduce it on OpenSuse Tumbleweed with LibreOffice 7.6.1.1. Since it seems to be caused by some interaction of packages in an OS version that is now outdated I think the bug can be closed. Having said that. An example document would simply be three lines of random text. Something like this: --- Here is the first line. Line two. Type your characters: Áóéí äëï etc. at the end of this line: Here is the last line. --- This can be copy-pasted into a blank document. The problem is font independent. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157162] Blank character in LibreOffice installation directory leads to error message when bootstrapping from Python script
https://bugs.documentfoundation.org/show_bug.cgi?id=157162 --- Comment #1 from Hossein --- Created attachment 189445 --> https://bugs.documentfoundation.org/attachment.cgi?id=189445=edit Screenshot of error dialog box, which says soffice.exe does not exist -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157162] New: Blank character in LibreOffice installation directory leads to error message when bootstrapping from Python script
https://bugs.documentfoundation.org/show_bug.cgi?id=157162 Bug ID: 157162 Summary: Blank character in LibreOffice installation directory leads to error message when bootstrapping from Python script Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: sdk Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: hoss...@libreoffice.org Created attachment 189444 --> https://bugs.documentfoundation.org/attachment.cgi?id=189444=edit A sample Python scripts that uses bootstrap() method Description: Having a blank character in LibreOffice installation directory leads to the display of an error message when bootstrapping from Python script. This is specially important on Windows where this is the default situation. The default Windows installation is in "C:\Program Files\LibreOffice", which contains a space character. Steps to Reproduce: 1. Download start.py from the attachment 1. Go to some folder, for example c:\windows\tmp 2. Run this command: "c:\Program Files\LibreOffice\program\python.exe" start.py If start.py is somewhere else, give the correct path. Actual Results: Dialog box, showing something like this: c:\Windows\Temp\Files\LibreOffice\program\soffice.exe does not exist. This string (wrong path) consists of: 1) Current working directory 2) Path to Python binary, cut after space character 3) soffice.exe The error dialog box says the soffice.exe (within the wrong path) does not exist. This shows that soffice.exe is called with wrong parameters, so that it wrongly assumes that this the above string is a file to open, and it gives error that it does not exist. It seems that the parameter handling routines do not care well enough about the possible space characters in the path. Expected Results: Invoking soffice.exe should happen with the correct parameters, and the error dialog box should not appear. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded A workaround is using short names, where applicable. For example, on Windows one can invoke: "c:\Progra~1\LibreOffice\program\python.exe" start.py In this case, the error dialog does not come up. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143002] [META] Tracked Changes of tables
https://bugs.documentfoundation.org/show_bug.cgi?id=143002 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156900 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156900 [Bug 156900] Delete row with track changes ON and show OFF doesn't hide the deleted row -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156900] Delete row with track changes ON and show OFF doesn't hide the deleted row
https://bugs.documentfoundation.org/show_bug.cgi?id=156900 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW CC||stephane.guillou@libreoffic ||e.org Keywords||bibisectRequest, regression Blocks||143002 --- Comment #2 from Stéphane Guillou (stragu) --- Thanks Telesto! Repro in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: beaea2e992912b4747d790070b26371f557b1f57 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded and: Version: 7.6.1.1 (X86_64) / LibreOffice Community Build ID: c7cda394c5de06de37d8109c310df89a4d4c3a98 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded No repro in: Version: 7.5.6.2 (X86_64) / LibreOffice Community Build ID: f654817fb68d6d4600d7d2f6b647e47729f55f15 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -> regression. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=143002 [Bug 143002] [META] Tracked Changes of tables -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156913] libreoffice-qt5 bug: unwanted line advance after deadkey (in libreoffice writer)
https://bugs.documentfoundation.org/show_bug.cgi?id=156913 Stéphane Guillou (stragu) changed: What|Removed |Added Version|unspecified |7.5.5.2 release Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- Can't reproduce in: Version: 7.6.1.1 (X86_64) / LibreOffice Community Build ID: c7cda394c5de06de37d8109c310df89a4d4c3a98 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: qt5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I installed libreoffice-qt5 as well. Can you provide an example document that makes it easy to test it, using a font that we all have? (e.g. Liberation Serif) Thank you! -- 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 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156920 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156920 [Bug 156920] [META] Textbox/Drawing Object autofit functionality -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156920] [META] Textbox/Drawing Object autofit functionality
https://bugs.documentfoundation.org/show_bug.cgi?id=156920 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||108741 Version|unspecified |Inherited From OOo Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108741 [Bug 108741] [META] Shapes bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108777] Undo doesnt restore original shape size after setting 'Resize shape to fit text'
https://bugs.documentfoundation.org/show_bug.cgi?id=108777 Stéphane Guillou (stragu) changed: What|Removed |Added Version|Inherited From OOo |5.2.0.4 release Summary|Undo doesnt work after |Undo doesnt restore |setting 'Resize shape to|original shape size after |fit text' |setting 'Resize shape to ||fit text' CC||caolan.mcnamara@collabora.c ||om, ||stephane.guillou@libreoffic ||e.org Keywords||implementationError See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=93 ||135 --- Comment #12 from Stéphane Guillou (stragu) --- This issue is not inherited: - In OOo 3.3, the option was greyed out. - Before 5.2.0.1, the option would not work - Since 5.2.0.1 and what I assume is Caolán fix for bug 93135, the feature works but the issue described here can be reproduced. (Checked with linux-64-releases bibisect repo.) So let's call it an implementation error. Copying Caolán in, in case you are interested. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157161] FILEOPEN DOCX: textbox (anchored in table, but NOT layout-in-cell) has wrong horizontal placement
https://bugs.documentfoundation.org/show_bug.cgi?id=157161 --- Comment #1 from Justin L --- Created attachment 189443 --> https://bugs.documentfoundation.org/attachment.cgi?id=189443=edit anchoredInCellTextbox2_mso2010.pdf -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157161] New: FILEOPEN DOCX: textbox (anchored in table, but NOT layout-in-cell) has wrong horizontal placement
https://bugs.documentfoundation.org/show_bug.cgi?id=157161 Bug ID: 157161 Summary: FILEOPEN DOCX: textbox (anchored in table, but NOT layout-in-cell) has wrong horizontal placement Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Keywords: filter:docx Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jl...@mail.com CC: jl...@mail.com Blocks: 104461 Created attachment 189442 --> https://bugs.documentfoundation.org/attachment.cgi?id=189442=edit anchoredInCellTextbox2.docx: textbox anchored in table cell, but not set to "Layout in cell" In MS Word, the textbox is placed over-top of the table. Steps to reproduce: 1.) open anchoredInCellTextbox2.docx Notice that the textbox is positioned on the side of the table. Although that looks nice, it should be positioned relative to the paragraph margin, not the table cell. This is inherited from OOo. This document didn't load both the table and the textbox until 3.6, where the position was already wrong. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=104461 [Bug 104461] [META] DOCX (OOXML) frame-related issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 104461] [META] DOCX (OOXML) frame-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=104461 Justin L changed: What|Removed |Added Depends on||157161 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157161 [Bug 157161] FILEOPEN DOCX: textbox (anchored in table, but NOT layout-in-cell) has wrong horizontal placement -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 137595] FILEOPEN DOCX shape size displayed in inches instead of cm
https://bugs.documentfoundation.org/show_bug.cgi?id=137595 --- Comment #5 from Justin L --- Created attachment 189441 --> https://bugs.documentfoundation.org/attachment.cgi?id=189441=edit anchoredInCellTextbox.docx repro 24.2+ I see the same thing with my document. The textbox loads in the same position as before, but now when you look at "Position and size", the wrong distances are shown, and hitting OK moves the textbox. I noticed that this can alter back and forth. I assume it is somehow related to the "maximum distance" allowed before hitting the edge of the page. Try changing the value to some large number (like 10cm) and notice that the UI reduces that number. Press OK, and then open the dialog again, and a different number with be shown, and quite likely a different maximum will also be allowed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 108640] [META] Object meta bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=108640 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||103494 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103494 [Bug 103494] [META] Textbox bugs and enhancements -- 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 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||108640 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=108640 [Bug 108640] [META] Object meta bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143344] [META] Linux Dark Mode bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=143344 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156916 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156916 [Bug 156916] Signature line uses dark icon with dark theme (KDE Plasma) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107237] [META] Notebookbar Tabbed
https://bugs.documentfoundation.org/show_bug.cgi?id=107237 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156916 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156916 [Bug 156916] Signature line uses dark icon with dark theme (KDE Plasma) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107139] [META] Breeze icons
https://bugs.documentfoundation.org/show_bug.cgi?id=107139 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156916 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156916 [Bug 156916] Signature line uses dark icon with dark theme (KDE Plasma) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156916] Signature line uses dark icon with dark theme (KDE Plasma)
https://bugs.documentfoundation.org/show_bug.cgi?id=156916 Stéphane Guillou (stragu) changed: What|Removed |Added Version|7.6.0.3 release |6.4.7.2 release CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Blocks||143344, 107139, 107237 Priority|medium |low Severity|normal |minor --- Comment #1 from Stéphane Guillou (stragu) --- Thank you for the report! Reproduced with: Version: 7.6.1.1 (X86_64) / LibreOffice Community Build ID: c7cda394c5de06de37d8109c310df89a4d4c3a98 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded As well as: Version: 6.4.7.2 Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US Calc: threaded That menu got icons in 6.4. This is for Breeze (dark). qt5 VCL plugin also affected. Not reproduced with dark variants of Colibre, Sifr or Sukapura. Does not happen with the standard toolbar. The main Insert menu does not have an icon for this command. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107139 [Bug 107139] [META] Breeze icons https://bugs.documentfoundation.org/show_bug.cgi?id=107237 [Bug 107237] [META] Notebookbar Tabbed https://bugs.documentfoundation.org/show_bug.cgi?id=143344 [Bug 143344] [META] Linux Dark Mode bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 81636] Not possible to view two formulas at the same time in different Calc instances
https://bugs.documentfoundation.org/show_bug.cgi?id=81636 --- Comment #25 from DErik --- Sorry if I came off a bit too strong. But take a look at the response I got on my initial bug report (https://bugs.documentfoundation.org/show_bug.cgi?id=157142). I didn't understand that explanation, not sure it is correct either, and it sounded like you weren't going to do anything about it. But it does need fixing. I'd do it myself, but I am not familiar enough with your code and implementation methods. I'm not on your development staff. And I would really appreciate it if it was fixed. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154463] Typing dots in Text Form Field crashes Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=154463
--- Comment #5 from Julien Nabet ---
Just for info, at the beginning when typing the fourth ".", I got:
"\a\003 \b"
69 for (SwNodeOffset n = nEndNode; nStartNode <= n; --n)
70 {
71 SwNode *const pNode(rNodes[n]);
72 if (pNode->IsTextNode())
73 {
74 SwTextNode & rTextNode(*pNode->GetTextNode());
when doing in gdb:
p rTextNode.GetText()
and everything is ok but LO reenters the same location (I suppose because of
autocorrect mechanism) and the string becomes:
"\a\003\a …. \b"
Notice both \a (which correspond to CH_TXT_ATR_FIELDSTART)
LO analyzes the string from end to start and when encounters
CH_TXT_ATR_FIELDSTART:
87 case CH_TXT_ATR_FIELDSTART:
88 --nFields;
89 assert(0 <= nFields);
90 break;
whereas in the first case when it's ok, it got there:
96 case CH_TXT_ATR_FIELDSEP:
97 if (nFields == 0)
98 {
99 assert(!ret); // one per field
100 ret.emplace(rTextNode, i - 1);
101 #ifndef DBG_UTIL
102 return *ret;
103 #endif
104 }
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 97213] PNG export of current sheet/page in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=97213 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEW |NEEDINFO --- Comment #5 from Stéphane Guillou (stragu) --- m.a.riosv from comment #4) > Export selection works for me in But have you tested _without_ selection? Could you ever reproduce Arnaud's results? If not, let's set back to needinfo and see if Arnaud can still reproduce. Duplicate bug 99359 was mainly about another issue, and there's no proof it actually exported several pages at once instead of one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156756] Icon sizes for the toolbar don't correspond to the actual sizes of icons
https://bugs.documentfoundation.org/show_bug.cgi?id=156756 --- Comment #4 from Faisal --- I can reproduce with Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 60(Build:3) CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US 7.6.0-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157036] LibreOffice 7.6 portable version can not achieve the following function insert->field (date, sheet name, document_title)
https://bugs.documentfoundation.org/show_bug.cgi?id=157036 ady changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 --- Comment #8 from ady --- (In reply to neil from comment #7) > Tried all of the above, but it still doesn't work. Please re-read comment 2. Before trying to insert a field, click first on the input box (formula bar). > Can't upload a picture to clearly show the problem I'm experiencing In the web page of the report bug 157036, there is a link "Add an attachment". Please don't set your own report to NEW. There is still no confirmation from someone else that there is a bug. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157160] New: [CRASH] New "Search" field in Options dialog crashes all the time
https://bugs.documentfoundation.org/show_bug.cgi?id=157160 Bug ID: 157160 Summary: [CRASH] New "Search" field in Options dialog crashes all the time Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: UI Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com I built LO from source today. I reset my user profile. If you search anything in the new search field of the Options dialog, LO will crash. Steps to reproduce: 1) Open any App (in my case it is Writer) 2) Go to Tools - Options 3) Type "Icon" in the search field 4) Do nothing else, just wait a few seconds 5) Crash System info Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 59bf2fbb5f6ebe62b4176c040054ff1c80e2d29a CPU threads: 16; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156839] Printing from macro creates empty page instead of the second sheet
https://bugs.documentfoundation.org/show_bug.cgi?id=156839 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||127592 CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 Whiteboard| QA:needsComment| --- Comment #3 from Stéphane Guillou (stragu) --- Tested with CUPS' print to pdf printer-driver-cups-pdf, set as default printer via File > Printer Settings...; which will output by default in ~/PDF. Reproduced that I'm getting two separate files without the content's of the second sheet: one page of sheet 1's contents, one empty page. Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: beaea2e992912b4747d790070b26371f557b1f57 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded In OOo 3.3, I also get just the first sheet, but no emtpy second document. So is this really a regression? 0b793116deaf35ce67245c1106e5ed5a722c7560 made it possible to export the second empty sheet, but it must have been considered to be empty before that. (In reply to Gabor Kelemen (allotropia) from comment #0) > The problematic behavior seems to happen only with the macro, not from the > Print dialog or from the CLI --convert-to pdf call. Alternatively, you can select both sheet tabs with Shift + Click, and both pages will have content. In a way, it's consistent with the setting... Are macros supposed to ignore in-app active selection? Or should this be fixed by moving the active selection in the macro instead? I guess oSheet.createCursorByRange() is already doing that in the macro... Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=127592 [Bug 127592] [META] LibreOffice Basic incl."Option Compatible" modules -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 127592] [META] LibreOffice Basic incl."Option Compatible" modules
https://bugs.documentfoundation.org/show_bug.cgi?id=127592 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156839 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156839 [Bug 156839] Printing from macro creates empty page instead of the second sheet -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157159] Text in comments has a white highlight
https://bugs.documentfoundation.org/show_bug.cgi?id=157159 --- Comment #1 from Faisal --- Screenshot uploaded as attachment 189440. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 106179] [META] Writer comment bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=106179 Faisal changed: What|Removed |Added Depends on||157159 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=157159 [Bug 157159] Text in comments has a white highlight -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157159] Text in comments has a white highlight
https://bugs.documentfoundation.org/show_bug.cgi?id=157159 Faisal changed: What|Removed |Added Blocks||106179 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=106179 [Bug 106179] [META] Writer comment bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157159] New: Text in comments has a white highlight
https://bugs.documentfoundation.org/show_bug.cgi?id=157159 Bug ID: 157159 Summary: Text in comments has a white highlight Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: leem...@protonmail.com Description: Text in comments has a white highlight behind them, even when the text is set to have no fill or no highlighting Steps to Reproduce: 1. Create a new document with a comment. 2. Enter text in comment. Actual Results: Text in the comment is highlighted in white. Expected Results: Text in the comment should not have any background color. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.6.0.3 (X86_64) / LibreOffice Community Build ID: 60(Build:3) CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-US (en_US.UTF-8); UI: en-US 7.6.0-1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
