[Bug 160825] The extension's "Release note" may be in an unintended format
https://bugs.documentfoundation.org/show_bug.cgi?id=160825 --- Comment #1 from nobu --- It's just a guess. This may happen if you make some of the text bold. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 95274] Wrong editing languages offered
https://bugs.documentfoundation.org/show_bug.cgi?id=95274 Heiko Tietze changed: What|Removed |Added CC|heiko.tietze@documentfounda | |tion.org| Keywords||needsUXEval Whiteboard|needsUXEval | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160610] Print multiple non-contiguous print ranges on a single page in LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160610 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO Keywords||needsUXEval --- Comment #3 from Heiko Tietze --- (In reply to Orwel from comment #0) > Would be great if the dimension of the paper allows it, a possibility to > print both ranges on one sheet would exist. Please elaborate a bit so we can see if this might be handy for the majority. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160760] Embedded SVG images rasterized when converted from ODM to ODT
https://bugs.documentfoundation.org/show_bug.cgi?id=160760 --- Comment #6 from ChenyHsu --- (In reply to V Stuart Foote from comment #4) > Were the source ODF documents used in the ODM prepared before you set > 'AddReplacementImages' false? If not, IIUC each will need to be reopened and > saved to remove the .PNG replacment. > > But I think you can go through and open each ODF archive and *remove* the > .PNG replacements. The .PNG from the Pictures directory, and in each > content.xml find the "
[Bug 157857] Ctrl+W closes all open documents, not just the active window
https://bugs.documentfoundation.org/show_bug.cgi?id=157857 Kira Tubo changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|UNCONFIRMED |RESOLVED --- Comment #7 from Kira Tubo --- (In reply to Damon Anderson from comment #5) > I also can not reproduce this bug. Thanks for confirming @Damon. I will go ahead and close this ticket. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing
https://bugs.documentfoundation.org/show_bug.cgi?id=160783 --- Comment #6 from Mike Kaganski --- Or maybe avoid trying to decode the version number, and just show the number as 32-bit hex like "0x12345678". This way, there wouldn't be a similarity to the vendor's "552.22.0.0" string, indicating clearly that the code uses internal encoding. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 136231] FILEOPEN PPTX: Text layout in text boxes is different in Impress than in PP (PPT is almost fine)
https://bugs.documentfoundation.org/show_bug.cgi?id=136231 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEW |RESOLVED Whiteboard||target:24.8.0 Resolution|--- |FIXED See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0609 CC||qui...@gmail.com, ||stephane.guillou@libreoffic ||e.org --- Comment #10 from Stéphane Guillou (stragu) --- Based on the obvious overlap issue in the first slide, resolved in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d4f6534e8870e8f271984c37ce54a6878f372ae1 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Fixed by: commit f61ea135430d7b4a1fac7de1e57a1314fbb1b49e author Tomaž Vajngerl Thu Mar 28 12:30:34 2024 +0900 committer Tomaž Vajngerl Wed Apr 03 04:06:50 2024 +0200 editeng: use text scaling that better mimics MSO text scaling Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165441 (build [52abeff6d5836b29dbefe69f284bbd89f6672ae2] in linux-64-24.8 repo) Thanks Quikee! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 139900] [META] PPTX Textbox related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=139900 Bug 139900 depends on bug 136231, which changed state. Bug 136231 Summary: FILEOPEN PPTX: Text layout in text boxes is different in Impress than in PP (PPT is almost fine) https://bugs.documentfoundation.org/show_bug.cgi?id=136231 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160609] PPTX : Arrow appears to be at wrong place due to the wrong line spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=160609 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||6231 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160783] Skia lib based Vulkan driver reporting issue, affect on GPU testing and deny listing
https://bugs.documentfoundation.org/show_bug.cgi?id=160783
--- Comment #5 from Mike Kaganski ---
The Vulkan API documents VkPhysicalDeviceProperties and its driverVersion this
way [1]:
> uint32_tdriverVersion;
> * driverVersion is the vendor-specified version of the driver.
> Note
> The encoding of driverVersion is implementation-defined. It may not use the
> same
> encoding as apiVersion. Applications should follow information from the vendor
> on how to extract the version information from driverVersion.
This explicitly tells that the encoding might be different in different
vendors. And discussion at [2] confirms that, showing that AMD seems to follow
Vilkan's apiVersion encoding scheme ("10|10|12"), while Intel and NVidia use
some own schemes (NVidia is said to use "10|8|8|6").
The GR_GL_DRIVER_VER macro can't be relevant here: it encodes three numbers
into a 64-bit number, with major part occupying bits in the higher 32 bits, and
only minor and point are in the lower 32 bits. Note that driverVersion in
VkPhysicalDeviceProperties is explicitly 32-bit.
I suppose, that the current code is OK for the task - considering only the
check part; all encodings seem to stick to the most important agreement, that
higher bits encode higher level of version number hierarchy. But if needed,
there could be a code that would decode the version into strings, taking the
vendor into account (just as a human-readable info, to match expectations).
[1]
https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkPhysicalDeviceProperties.html
[2]
https://www.reddit.com/r/vulkan/comments/fmift4/how_to_decode_driverversion_field_of/
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160609] PPTX : Arrow appears to be at wrong place due to the wrong line spacing
https://bugs.documentfoundation.org/show_bug.cgi?id=160609 Stéphane Guillou (stragu) changed: What|Removed |Added CC||qui...@gmail.com, ||stephane.guillou@libreoffic ||e.org Version|24.2.0.3 release|Inherited From OOo Whiteboard||target:24.8.0 Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #7 from Stéphane Guillou (stragu) --- Reproduced in: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded ... and in all sorts of different ways all the way back to OOo 3.3. Resolved in: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: d4f6534e8870e8f271984c37ce54a6878f372ae1 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded Bibisected the fix to: commit f61ea135430d7b4a1fac7de1e57a1314fbb1b49e author Tomaž Vajngerl Thu Mar 28 12:30:34 2024 +0900 committer Tomaž Vajngerl Wed Apr 03 04:06:50 2024 +0200 editeng: use text scaling that better mimics MSO text scaling Reviewed-on: https://gerrit.libreoffice.org/c/core/+/165441 (build [52abeff6d5836b29dbefe69f284bbd89f6672ae2] in linux-64-24.8 repo) Thanks Quikee! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160619] Create Separate Print Jobs for collated output fails
https://bugs.documentfoundation.org/show_bug.cgi?id=160619 --- Comment #3 from Robert Marmorstein --- And here is my version information (though I've experienced this through several versions now) Version: 7.6.5.2 (X86_64) / LibreOffice Community Build ID: 60(Build:2) CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 4:7.6.5-0ubuntu0.23.10.1 Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160619] Create Separate Print Jobs for collated output fails
https://bugs.documentfoundation.org/show_bug.cgi?id=160619 --- Comment #2 from Robert Marmorstein --- I've actually experienced this with multiple printers: a Brother DCP-L2550DW and an HP LaserJet 1022N. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160619] Create Separate Print Jobs for collated output fails
https://bugs.documentfoundation.org/show_bug.cgi?id=160619 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #1 from Stéphane Guillou (stragu) --- (In reply to Robert Marmorstein from comment #0) > However, if I double click both these options, it works correctly every time. What are the two options? "Create separate print jobs for collated output" and ...? Can you please also: - share your printer model - paste here the version info copied with the button in the dialog Help > About LibreOffice Thank you. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 142074] [META] Application Colours settings bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=142074 Bug 142074 depends on bug 157240, which changed state. Bug 157240 Summary: PRINTING text lines disappear (in fact become white) when printing in grayscale https://bugs.documentfoundation.org/show_bug.cgi?id=157240 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158315] [META] Regressions from scaled glyph positions refactoring
https://bugs.documentfoundation.org/show_bug.cgi?id=158315 Bug 158315 depends on bug 157240, which changed state. Bug 157240 Summary: PRINTING text lines disappear (in fact become white) when printing in grayscale https://bugs.documentfoundation.org/show_bug.cgi?id=157240 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160827] New: Crash on opening certain .docx files
https://bugs.documentfoundation.org/show_bug.cgi?id=160827 Bug ID: 160827 Summary: Crash on opening certain .docx files Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: dan...@clintelsystems.com Created attachment 193857 --> https://bugs.documentfoundation.org/attachment.cgi?id=193857&action=edit Example document $ libreoffice "/home/doconnor/Downloads/updated-specifications-for-revisions-to-the-victorian-admitted-episodes-dataset-(vaed)-for-2024.docx" Immediate crash. Unfortunately, I don't have any other useful error logs, output or similar to help classify further. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160586] LibreOffice 7.6 does not load under Windows 10 64 bit.
https://bugs.documentfoundation.org/show_bug.cgi?id=160586 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160626] Selecting a style in the toolbar list sends it at the bottom of the list
https://bugs.documentfoundation.org/show_bug.cgi?id=160626 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157857] Ctrl+W closes all open documents, not just the active window
https://bugs.documentfoundation.org/show_bug.cgi?id=157857 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.
[Bug 157857] Ctrl+W closes all open documents, not just the active window
https://bugs.documentfoundation.org/show_bug.cgi?id=157857 --- Comment #6 from QA Administrators --- [Automated Action] NeedInfo-To-Unconfirmed -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157155] Display of same document in multiple windows in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=157155 QA Administrators changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 157155] Display of same document in multiple windows in Writer
https://bugs.documentfoundation.org/show_bug.cgi?id=157155 --- Comment #5 from QA Administrators --- Dear kaesezeh, 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.
[Bug 157958] Fails to Save Document with "General input/output error" message.
https://bugs.documentfoundation.org/show_bug.cgi?id=157958 --- Comment #4 from QA Administrators --- Dear documentfoundation, 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.
[Bug 157957] Calc crashes when copying data to clipboard
https://bugs.documentfoundation.org/show_bug.cgi?id=157957 --- Comment #3 from QA Administrators --- Dear kb.claim, 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.
[Bug 157954] Symbols not displaying consistently
https://bugs.documentfoundation.org/show_bug.cgi?id=157954 --- Comment #3 from QA Administrators --- Dear Peter Wilkins, 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.
[Bug 157653] (Not Responding) Message appears constantly when using Spreadsheet
https://bugs.documentfoundation.org/show_bug.cgi?id=157653 --- Comment #4 from QA Administrators --- Dear Deanna, 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.
[Bug 73971] FILEOPEN: PPT file will not open if set password to modify (no problem with PPTX)
https://bugs.documentfoundation.org/show_bug.cgi?id=73971 --- Comment #18 from QA Administrators --- Dear Mack, 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.
[Bug 144243] FILEOPEN PPTX Numbering formatting imported only for previous numbering levels
https://bugs.documentfoundation.org/show_bug.cgi?id=144243 --- Comment #3 from QA Administrators --- Dear NISZ LibreOffice Team, 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.
[Bug 142211] .uno:DataRanges command is missing in Chart's Customize dialog
https://bugs.documentfoundation.org/show_bug.cgi?id=142211 --- Comment #2 from QA Administrators --- Dear Mike Kaganski, 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.
[Bug 142191] SVG export excludes graphic items with hyperlink using javascript
https://bugs.documentfoundation.org/show_bug.cgi?id=142191 --- Comment #4 from QA Administrators --- Dear Ned, 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.
[Bug 142156] Font position changes to Subscript, if style isn't inherited from another style
https://bugs.documentfoundation.org/show_bug.cgi?id=142156 --- Comment #9 from QA Administrators --- Dear Georgy Litvinov, 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.
[Bug 136923] Export to PDF/A is not PDF/A conformant (ISO 19005-1:2005, Clause: 6.1.12, Test number: 5 - Maximum capacity of an array (in elements) is 8191)
https://bugs.documentfoundation.org/show_bug.cgi?id=136923 --- Comment #8 from QA Administrators --- Dear jan.prochaska, 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.
[Bug 140672] Undefined values (empty cell) being treated as zero in table formulas
https://bugs.documentfoundation.org/show_bug.cgi?id=140672 --- Comment #5 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.
[Bug 111070] Saving file with a different LO-recognized file extension does not add correct extension
https://bugs.documentfoundation.org/show_bug.cgi?id=111070 --- Comment #16 from QA Administrators --- Dear Aron Budea, 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.
[Bug 108189] inspection of object hangs LO - memory leak
https://bugs.documentfoundation.org/show_bug.cgi?id=108189 --- Comment #13 from QA Administrators --- Dear Oliver Brinzing, 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.
[Bug 160610] Print multiple non-contiguous print ranges on a single page in LibreOffice Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=160610 Stéphane Guillou (stragu) changed: What|Removed |Added Summary|Print multiple |Print multiple |non-contiguous ranges on a |non-contiguous print ranges |single page in LibreOffice |on a single page in |Calc|LibreOffice Calc CC||libreoffice-ux-advise@lists ||.freedesktop.org, ||stephane.guillou@libreoffic ||e.org Version|unspecified |24.2.2.2 release --- Comment #2 from Stéphane Guillou (stragu) --- UX/Design team, what do you think? Something like "suppress space between print ranges"? Sounds prone to complications. I also tested printing only "selected cells" to no avail: it prints whatever is in between the ranges too. As a cumbersome workaround: 1. Hide columns/rows 2. Define a single print range 3. Print -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160824] Print dialogue box is scrollable for number of copies leading to excess copies being printed on accident
https://bugs.documentfoundation.org/show_bug.cgi?id=160824 m_a_riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160826] Spell check on Lubuntu
https://bugs.documentfoundation.org/show_bug.cgi?id=160826 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #1 from Stéphane Guillou (stragu) --- Can you see an English dictionary in your Tools > Extensions? If not, have you tried: - installing this dictionary? https://extensions.libreoffice.org/en/extensions/show/english-dictionaries - installing the language pack from Ubuntu repos: sudo apt install libreoffice-l10n-en-gb If that still does not work, please install a version of LibreOffice that is still maintained, currently 7.6 or 24.2. Deb packages are on https://www.libreoffice.org/download/download/, alternatively use a PPA: https://launchpad.net/~libreoffice/+archive/ubuntu/ppa ...and let us know if the issue persists. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160612] LibreOffice Writer failed to auto-save my work, so it was lost when Windows ran a software update
https://bugs.documentfoundation.org/show_bug.cgi?id=160612 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||stephane.guillou@libreoffic ||e.org --- Comment #2 from Stéphane Guillou (stragu) --- If you had AutoRecovery set up, changes should have been saved during idling. On top of m_a_riosv's question about having autosave set up, I'd recommend updating to version 24.2, which now has AutoRecovery and Backup Copies turned on by default (on a new profile), along with some bug fixes. Please see: https://wiki.documentfoundation.org/ReleaseNotes/24.2#Core_/_General If you didn't have AutoRecovery turned on, I'd say we can mark this as duplicate of bug 152463. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160826] New: Spell check on Lubuntu
https://bugs.documentfoundation.org/show_bug.cgi?id=160826 Bug ID: 160826 Summary: Spell check on Lubuntu Product: LibreOffice Version: 7.3.7.2 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: smontalv...@outlook.com Description: No matter what I do or how many downloads I've tried, the spell check will not work. everything works fine on Mint and Ubuntu on other computers I use, but on my older laptop running Lubuntu officelibre works great, but it will not spell check. I have to type them, send then to another computer just to check the spelling. I've checked all the setting looking at one computer to the other, and everything is exactly the same. but no spell check on Lubuntu. DEFAULT English USA is selected but no green check mark, and under spell check it says NONE under "test languages". I've done all i know to do. Actual Results: it just doesn't work. Expected Results: it doesn't work Reproducible: Always User Profile Reset: Yes Additional Info: work. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160825] New: The extension's "Release note" may be in an unintended format
https://bugs.documentfoundation.org/show_bug.cgi?id=160825 Bug ID: 160825 Summary: The extension's "Release note" may be in an unintended format Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Extensions Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: tac...@hotmail.co.jp Description: The extension's "Release note" may be in an unintended format. Steps to Reproduce: 1. View the Release note for the next extension https://extensions.libreoffice.org/en/extensions/show/34164 https://extensions.libreoffice.org/en/extensions/show/41989 https://extensions.libreoffice.org/en/extensions/show/42000 Actual Results: 2. The content may be the same as the format of the title. This is not what the author intended. Expected Results: 2. The content is not formatted as a title. Reproducible: Always User Profile Reset: No Additional Info: A lot of people have noticed this. The reporting place may not be here. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160614] Master document - Incorrect index page numbers in subdocuments
https://bugs.documentfoundation.org/show_bug.cgi?id=160614 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |NOTABUG CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED Whiteboard| QA:needsComment| --- Comment #2 from Stéphane Guillou (stragu) --- That's the case at fileopen, but an update of the fields adapts the page numbers. (Tools > Update > Update all) Does that not work for you? Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160618] LibreOffice (Draw) can't rotate orientation (landscape document into portrait) for printing
https://bugs.documentfoundation.org/show_bug.cgi?id=160618 Stéphane Guillou (stragu) changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO CC||stephane.guillou@libreoffic ||e.org --- Comment #6 from Stéphane Guillou (stragu) --- Thanks for the report. Can you please: - share the document your are trying to print - provide more precise steps to detail what settings you have tried - try the settings Stuart suggested - share the full version info copied with the button in Help > About LibreOffice -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155607] EDITING. Selecting a cell on one side of a screen splitter/divider-bar scrolls that cell into view on the other side of the bar
https://bugs.documentfoundation.org/show_bug.cgi?id=155607 Stéphane Guillou (stragu) changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |WORKSFORME --- Comment #11 from Stéphane Guillou (stragu) --- Thank you for testing again. Let's close this one as "works for me" then, as we're not sure what fixed it. Please open a new report for each single enhancement request you've identified (e.g. control position). Thanks! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Bug 80430 depends on bug 155882, which changed state. Bug 155882 Summary: "Recency" is not explained in Navigator https://bugs.documentfoundation.org/show_bug.cgi?id=155882 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 115673] [META] Navigate By toolbar control bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=115673 Bug 115673 depends on bug 156273, which changed state. Bug 156273 Summary: Add a "Navigate by" Help page for .uno:NavElement https://bugs.documentfoundation.org/show_bug.cgi?id=156273 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 80430] [META] Documentation gap for new features
https://bugs.documentfoundation.org/show_bug.cgi?id=80430 Bug 80430 depends on bug 156273, which changed state. Bug 156273 Summary: Add a "Navigate by" Help page for .uno:NavElement https://bugs.documentfoundation.org/show_bug.cgi?id=156273 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160824] New: Print dialogue box is scrollable for number of copies leading to excess copies being printed on accident
https://bugs.documentfoundation.org/show_bug.cgi?id=160824 Bug ID: 160824 Summary: Print dialogue box is scrollable for number of copies leading to excess copies being printed on accident Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Draw Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: themitochondr...@gmail.com Description: Wanted to print 2 pages. The print dialogue box automatically selects the number of copies box which is then scrollable to enormous quantities by accident. When I got to the printer it was printing hundreds of copies of my document instead of 1. Please don't make the number of copies box scrollable from the mousepad. Steps to Reproduce: 1. Ctrl + P on a document 2.Scroll on track pad 3.Press enter and way too many copies print Actual Results: printed one hundred pages of a document that was sensitive and needed shredding in lots of 4 through the shredder. Expected Results: Print 2 pages once only Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: DrawingDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Bug 159375] Opening Tools > Options dialog takes too long
https://bugs.documentfoundation.org/show_bug.cgi?id=159375 --- Comment #12 from Bayram Çiçek --- (In reply to Hossein from comment #11) > (In reply to Bayram Çiçek from comment #9) > > > I think another approach can be creating a search database at compile > > > time. > > > In this way, it will be ready at execution time, without any delays. You > > > may > > > initialize the dialogs, dump strings and write them to some files, and > > > then > > > re-use that at runtime. You may need to do this for each and every > > > language, > > > as the translations are important here. > > We tried this approach but we saw that this approach makes the > > implementation more complex - especially when it comes to different > > languages (translations etc...) > Could you please describe how did you try this approach? The latest work done about this approach was in patchset 15 (and in previous ones): https://gerrit.libreoffice.org/c/core/+/152519/15 > And what were the issues that made it so complex? As far as I remember, there were some improvements needed in some makefiles (e.g. solenv/gbuild/UIConfig.mk), also further work needed to be done such as fetching the generated data at run-time, localization etc. I had a limited time to implement this idea and we couldn't estimate the time needed for this build-time extraction approach. I agree that this build-time approach is the best way to implement the idea - without initializing all dialogs at the start of Options dialog. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160823] PRINTING PDF Allow to select which section to print/export
https://bugs.documentfoundation.org/show_bug.cgi?id=160823 m_a_riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160816] Can't paste text copied from PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=160816 --- Comment #3 from stokest...@gmail.com --- Created attachment 193856 --> https://bugs.documentfoundation.org/attachment.cgi?id=193856&action=edit screen grab of the bug in action -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160816] Can't paste text copied from PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=160816 --- Comment #2 from stokest...@gmail.com --- Thanks for the follow-up, but no... no clipboard manager. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 --- Comment #9 from Oleksandr Natalenko --- I've also managed to collect `perf` data for `soffice.bin` burning CPU: ``` # perf record -ag -p $(pidof soffice.bin) # …wait ~10 seconds… # perf report --sort=comm --stdio … # Children Self Command # ... # 99.97%99.97% soffice.bin | ---(anonymous namespace)::HTMLEndPosLst::InsertNoScript(SfxPoolItem const&, int, int, std::set >, comphelper::UniquePtrValueLess, std::allocator > > >&, bool) [clone .part.0] … ``` This stuff seems to be a part of `/usr/lib/libreoffice/program/libswlo.so`. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 120078] When inserting snap guide lines, the position should be relative to page, not margin
https://bugs.documentfoundation.org/show_bug.cgi?id=120078 --- Comment #8 from romain2b...@yahoo.fr --- Reproduced in: Version: 7.6.6.3 (X86_64) / LibreOffice Community Build ID: d97b2716a9a4a2ce1391dee1765565ea469b0ae7 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160315] Saving files to SMB3 network shares no longer works
https://bugs.documentfoundation.org/show_bug.cgi?id=160315 --- Comment #7 from Ettore Atalan --- libreoffice-kf5 is probably not the cause of the problem, since KDE Plasma is not used on the computer where LibreOffice encounters this problem. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160823] New: PRINTING PDF Allow to select which section to print/export
https://bugs.documentfoundation.org/show_bug.cgi?id=160823 Bug ID: 160823 Summary: PRINTING PDF Allow to select which section to print/export Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: romain2b...@yahoo.fr Both Print dialog and Export in PDF dialog allow to select which page to print/export. When you want to limit to certain sections of the document, one needs to identify on which page they are. Proposal is to allow the user to select sections/part of the tree of headings and the software will determine which pages to print/export. It can be done by having the option to select headings or by having a window to select the headings and then it populates the Page field to print/export. When reviewing a document (in paper) or sharing it, such function would be very handy. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160439] rounding error
https://bugs.documentfoundation.org/show_bug.cgi?id=160439 --- Comment #2 from JkUsr --- I have the same problem, with a different calculation: # FormulaDisplay A1 100.3 100.3 A2 =A1*0.15 15.045 A3 =A215.04 A4 =ROUND(A2,2) 15.05 A3 have 0.00 Format Code, other cells have General format code. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155607] EDITING. Selecting a cell on one side of a screen splitter/divider-bar scrolls that cell into view on the other side of the bar
https://bugs.documentfoundation.org/show_bug.cgi?id=155607 --- Comment #10 from Greg --- This seems to have been fixed for the release I'm using: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 32; OS: Linux 6.8; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155607] EDITING. Selecting a cell on one side of a screen splitter/divider-bar scrolls that cell into view on the other side of the bar
https://bugs.documentfoundation.org/show_bug.cgi?id=155607 --- Comment #9 from Greg --- This seems to have been fixed for the release I'm using: Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: 420(Build:2) CPU threads: 32; OS: Linux 6.8; UI render: default; VCL: kf5 (cairo+wayland) Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160813] LibreOffice Writer - Tabbed UI not scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=160813 --- Comment #7 from V Stuart Foote --- > > Like seriously, I made an effort to report something that clearly shouldn't > be the way it is (did I know that this was due native MS API, absolutely > not). The second part is a discussion why it might be important, but totaly > understandable when the focus is on Linux. > > Thanks anyways for explaining the cause of this, have a good day. OK, you're welcome. And, please don't be put off by comments I wrote, which on rereading were a bit brusque, sorry. I/we do appreciate the concern you obviously had, and also that you took the effort to go ahead and file a BZ issue. LibreOffice and the Document Foundation are driven by a volunteer community. We don't expect everyone to know everything realizing we all have to start somewhere--please keep contributing, Bugzilla submissions are just one means to participate. Check out the 'Get Involved' link [1] on the Help menu. Please stay around. =-ref-= [1] https://www.libreoffice.org/community/get-involved -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160315] Saving files to SMB3 network shares no longer works
https://bugs.documentfoundation.org/show_bug.cgi?id=160315 --- Comment #6 from Andreas B. Mundt --- We see something comparable, documented here: https://bugs.debian.org/1069835 For us, removing the libreoffice-kf5 package used on the KDE plasma desktop makes the issue go away?! -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 --- Comment #8 from Oleksandr Natalenko --- Created attachment 193854 --> https://bugs.documentfoundation.org/attachment.cgi?id=193854&action=edit Stacktrace with SAL_USE_VCLPLUGIN=kf6 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 --- Comment #7 from Oleksandr Natalenko --- Also, we use SAL_USE_VCLPLUGIN=gtk3 due to https://bugs.documentfoundation.org/show_bug.cgi?id=160416 / https://bugs.documentfoundation.org/show_bug.cgi?id=160565 / https://bugs.documentfoundation.org/show_bug.cgi?id=160624 The issue is reproducible with SAL_USE_VCLPLUGIN=kf6 too, but it may happen that it is triggered on Writer closure. With SAL_USE_VCLPLUGIN=kf6 the top part of the stack looks very similar. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822
--- Comment #6 from Oleksandr Natalenko ---
We don't have any 3rd-party clipboard manager except the one KDE offers
("Clipboard Contents" in the systray). I tried marking it as "Disabled", but it
didn't help.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #5 from m_a_riosv --- Perhaps some clipboard manager interfering? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160820] Slideshow two presentations simultaneously on two different monitors
https://bugs.documentfoundation.org/show_bug.cgi?id=160820 m_a_riosv changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug.
[Bug 99096] The ability to select and copy multiple footnotes/endnotes (into a new document)
https://bugs.documentfoundation.org/show_bug.cgi?id=99096 m_a_riosv changed: What|Removed |Added CC||jens.d...@live.de --- Comment #5 from m_a_riosv --- *** Bug 160818 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160818] Copy/Paste does not copy footnotes
https://bugs.documentfoundation.org/show_bug.cgi?id=160818 m_a_riosv changed: What|Removed |Added Resolution|--- |DUPLICATE CC||miguelangelrv@libreoffice.o ||rg Status|UNCONFIRMED |RESOLVED --- Comment #1 from m_a_riosv --- *** This bug has been marked as a duplicate of bug 99096 *** -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160816] Can't paste text copied from PDFs
https://bugs.documentfoundation.org/show_bug.cgi?id=160816 m_a_riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m_a_riosv --- Not reproducible with Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded Maybe you have some clipboard manager installed? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 --- Comment #4 from Oleksandr Natalenko --- We both use KDE 6. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160813] LibreOffice Writer - Tabbed UI not scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=160813 --- Comment #6 from quach...@duck.com --- >What makes you think you are the first to observe this inadequacy? And, why >>should you as a casual user "expect" an open source and very "cross-platform" >>project to do anything? Have you tested on the other os/DE to be able to make >>informed suggestions? I am not the first to observe this, otherwise I wouldn't link a webpage from someone else describing this. I haven't found a solution for this, explains why I reported this in the first place (is it a bug, isn't it a bug, how should I know this as a first time user that did look in the web for a solution). Changing the text size to 170% did not solve this for me. If this isn't a priority for the devs, then that's fair enough. I can live with it, and I would be fine with the response before, just got upset with the 'and?' at the beginning. Like seriously, I made an effort to report something that clearly shouldn't be the way it is (did I know that this was due native MS API, absolutely not). The second part is a discussion why it might be important, but totaly understandable when the focus is on Linux. Thanks anyways for explaining the cause of this, have a good day. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 --- Comment #3 from Oleksandr Natalenko --- I do have actual cores saved as well, so I can peek into them further and provide any additional information needed. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 --- Comment #2 from Oleksandr Natalenko --- Created attachment 193853 --> https://bugs.documentfoundation.org/attachment.cgi?id=193853&action=edit Writer core from my desktop -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 --- Comment #1 from Oleksandr Natalenko --- Created attachment 193852 --> https://bugs.documentfoundation.org/attachment.cgi?id=193852&action=edit Writer core from wife's laptop -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158304] Cross-fade dialogs settings are not loaded after LO restart
https://bugs.documentfoundation.org/show_bug.cgi?id=158304 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #4 from Gabor Kelemen (allotropia) --- Proposed patch: https://gerrit.libreoffice.org/c/core/+/166633 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158305] Convert to polygon dialogs settings are not loaded after LO restart
https://bugs.documentfoundation.org/show_bug.cgi?id=158305 Gabor Kelemen (allotropia) changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #4 from Gabor Kelemen (allotropia) --- Proposed patch: https://gerrit.libreoffice.org/c/core/+/166631 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160822] New: Writer hangs on copying text with Ctrl+C
https://bugs.documentfoundation.org/show_bug.cgi?id=160822 Bug ID: 160822 Summary: Writer hangs on copying text with Ctrl+C Product: LibreOffice Version: 24.2.2.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: oleksa...@natalenko.name Description: My wife writes her Master's thesis with LibreOffice, and when she copy-pastes some text within the document, Writer may, or may not, hang after pressing Ctrl+C. This happens with some text only, sometimes we can narrow this down to a particular word that needs to be copy-pasted for the issue to be triggered. The issue can be reliably reproduced. The text that triggers this may be different (like, in different places of the document), but once the nasty snippet is found, copying it each time triggers the bug. The issue manifests in Writer going completely unresponsive just burning the CPU. I've managed to collect two cores / stacktraces, one on my wife's laptop where the issue can be triggered reliably, another one is on my desktop, where it can take some time after selecting the text and copying it for the bug to occur (the text remains selected, and I just watch Writer waiting for it to become unresponsive). We both have the same distro with the same set of packages, so I don't know why it is harder to reproduce the bug on my desktop. I will attach stack traces as separate files. Steps to Reproduce: 1. select some text 2. hit Ctrl+C Actual Results: Writer goes unresponsive burning CPU. Expected Results: Copy-paste should just work. Reproducible: Sometimes User Profile Reset: Yes Additional Info: It's libreoffice-fresh from Arch Linux, everything is up-to-date. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160821] New: Calc: Establish link between two sheeets; going back to 'link from' sheet stops the process
https://bugs.documentfoundation.org/show_bug.cgi?id=160821 Bug ID: 160821 Summary: Calc: Establish link between two sheeets; going back to 'link from' sheet stops the process Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: falk-kamme...@mail.tele.dk Description: In 'link to' cell I insert =. When clicking on 'link from' sheet, I observe a small shiver on the screen, but nothing happens. When clicking again, 'link from' sheet opens, but clicking on 'link from' cell does not produce a link. Have tried with Ctrl+PageUp with same result.The critical thing is inserting the = in 'link to' cell. Have tried writing the cell-reference, that works, but with 300 links to do...!!! Deleted version 24.2.2.2 and installed 7.6.6 with same result. Also with 7.6.4 In the beginning, the problem did not accur when I closed the application and reopened it again. But now it happens every time. Steps to Reproduce: 1.insert = i 'link to' cell 2.click on 'link from' sheet 3. Actual Results: Then the problem comes: a 'shiver' on the screen, but I stay on the 'link to' sheet. When I click a second time, the 'link from' sheet opens, but an 'enter' on the 'link from' cell does not produce any link. Expected Results: It should have opened the 'link from' sheet Reproducible: Always User Profile Reset: Yes Additional Info: It is not possible to copy anything from that page. The normal copy function does not work. Version: 24.2.2.2 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160813] LibreOffice Writer - Tabbed UI not scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=160813 --- Comment #5 from V Stuart Foote --- (In reply to quachvan from comment #4) > I understand your explanations, just as feedback, never reply a request with > and? > Someone in this world makes an effort to report something and instead of > being grateful for that, you trigger a defensive mechanism. > Kind of an entitled ask, best to quash out of the gate, => NAB nor a well stated enhancement request. What makes you think you are the first to observe this inadequacy? And, why should you as a casual user "expect" an open source and very "cross-platform" project to do anything? Have you tested on the other os/DE to be able to make informed suggestions? For example have you checked the behavior with adjusted Display and Text scaling as noted in comment 2? > I don't know for whom you LibreOffice developers are doing this, but it's no > secret that most computers run Windows and if you want to grow your customer > base, make the on-boarding from MS Office to LibreOffice as smooth as > possible. Well, that is a long running discussion. Doing more requires a major investment in the native code needed to fully implement os/DE specific source needed to move LibreOffice fully to a MS Ribbon style UI *cross-platform*, with the majority of developers interested in Linux os/DE issues and support of the ODF document model and interoperability with MS's OOXML document model. The current GTK UI and UNO assemblages, known as MUFFIN, only get us so far. And there is little developer interest to implement unnecessary native MS or Apple API calls to replace what are currently implemented cross platform. Native API support for Windows or macOS is not a very high priority, only what is functionally necessary. If you are interested in issues around adopting the Tabbed UI as default, see bug 135501, and from there links to related Notebook Bar issues. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155607] EDITING. Selecting a cell on one side of a screen splitter/divider-bar scrolls that cell into view on the other side of the bar
https://bugs.documentfoundation.org/show_bug.cgi?id=155607 Stéphane Guillou (stragu) changed: What|Removed |Added Status|REOPENED|NEEDINFO --- Comment #8 from Stéphane Guillou (stragu) --- Bug reports should be about one single issue. Let's focus on what's in the summary: focus moving on one side of the splitter when interacting with the other. (Regarding the position of the controls, please open a new report.) (In reply to Greg from comment #0) > My expected behaviour is that on the right the content doesn't scroll in > response to selection on the left. I can't reproduce that with: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 695e8742da850bbb15c2e6d2b5d4c99a0daf4925 CPU threads: 8; OS: Linux 6.5; UI render: default; VCL: gtk3 Can you please test again in a recent version, preferably 24.2? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155633] Can't use a custom bibliography database source for Insert > TOC & Indexes > Bibliography Entry
https://bugs.documentfoundation.org/show_bug.cgi?id=155633 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 103610] [META] Slide show (presentation mode) bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103610 Eyal Rozenberg changed: What|Removed |Added Depends on||160820 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=160820 [Bug 160820] Slideshow two presentations simultaneously on two different monitors -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160820] Slideshow two presentations simultaneously on two different monitors
https://bugs.documentfoundation.org/show_bug.cgi?id=160820 Eyal Rozenberg changed: What|Removed |Added Blocks||103610 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103610 [Bug 103610] [META] Slide show (presentation mode) bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160820] Slideshow two presentations simultaneously on two different monitors
https://bugs.documentfoundation.org/show_bug.cgi?id=160820 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0242 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160242] Enhancement: Make possible 2 or more impress in fullscreen each on a dedicated monitor AND each seekable indipendently with user-defined hotkeys per each file.
https://bugs.documentfoundation.org/show_bug.cgi?id=160242 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=16 ||0820 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160820] New: Slideshow two presentations simultaneously on two different monitors
https://bugs.documentfoundation.org/show_bug.cgi?id=160820 Bug ID: 160820 Summary: Slideshow two presentations simultaneously on two different monitors Product: LibreOffice Version: 24.2.2.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Suppose I have two different presentations I've opened in Impress, and two different monitors connected to my computer. I would like to be able to "slideshow" both presentations at once on my two monitors, without them interfering with each other. AFAICT, this is not currently doable. Notes: * This bug is not about how exactly the progression through each of the two slideshows is to be managed. * This is a part of the ask in bug 160242, which combined too many things it seems. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 129062] [META] Skia library bugs
https://bugs.documentfoundation.org/show_bug.cgi?id=129062 Bug 129062 depends on bug 160757, which changed state. Bug 160757 Summary: cant start libre office except in safe mode (Skia / Vulkan) https://bugs.documentfoundation.org/show_bug.cgi?id=160757 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160757] cant start libre office except in safe mode (Skia / Vulkan)
https://bugs.documentfoundation.org/show_bug.cgi?id=160757 V Stuart Foote changed: What|Removed |Added Resolution|--- |NOTABUG Status|NEW |RESOLVED --- Comment #13 from V Stuart Foote --- (In reply to colourfuldesu from comment #10) > https://youtu.be/lXYnAcrZVzI > > I tested a bit, if I disable "use skia for all rendering", I can launch > LibreOffice just as if I enable "use skia for all rendering" and "force skia > software rendering" but this time 0:20, I cant launch LibreOffice if I just > disable skia at all > > 0:40 then I try to using dgpu then switch to igpu, no change > > 1：20 I enable force skia through config and LibreOffice can launch > > so the fix is if I disable skia, it launch. If I enable skia AND force skia, > it launch. but I need to do the 2nd solution to make libre launch with > disabled skia. > > somehow if I force enable skia in safe mode, the settings just reverts back > that I need to configure it though config file. > > I dont know how do I make my dgpu RX5500M came up in vulkan mode, I would > prefer it to be the other igpu for battery life reasons > > sorry for the late reply, iam just really lazy in college hahaha The "Switchable Graphics" of making LibreOffice a High Performance is not helping as the Skia Vulkan rendering for the dGPU is failing graphics tests just as the iGPU on the APU is. Simply put, it looks like you will not be able to run LibreOffice with Skia / Vulkan vector shaders. Might improve with an AMD Vulkan driver change, or not. Otherwise, stay out of the SafeMode for doing configuration--it doesn't persist. And, your LibreOffice install behaves as expected. Editing the registrymodification.xcu to copy in the UseSkia and ForceSkiaRaster stanzas at the 1:18 mark is all that you need. Edit to toggle the ForceSkiaRaster "True" at 5:10 mark is where you need to be for running LibreOffice. You can edit it to "False" to test the Vulkan rendering (with either GPU set from "Switchable Graphics"). And if/when the Vulkan graphics tests fail, the stanza will be reset to "True"--leaving you with UseSkia and ForceSkiaRaster both true. You can set both "False" to force GDI rendering paths, non-Skia. To be able to denylist your AMD RX 5500M dGPU (which actually only avoids running the Vulkan graphics testing and sets ForceSkiaRaster) we add the device and Vulkan driver details to the denylist. We have both the iGPU, and dGPU details in comment 7 from GLview, just a little reluctant to deny both as we've had other OpenGL era and Vulkan issues with AMD "Switchable Graphics" (Adrenaline, or Win10/11 integrated) and nVidia "Optimus" (nVidia control panel, or Win10/11 integrated). So, I think you are good for now--but check your drivers from time to time and see if Vulkan behaves. Setting => NAB as the Skia tests are doing what they should, and we can't really control the Vulkan driver support per GPU. p.s. -- noticed you have the Java based Nonlinear Solver extension enabled in your install, you can uncheck it in the install wizard and that will save several seconds of config during LO launch. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160813] LibreOffice Writer - Tabbed UI not scaled
https://bugs.documentfoundation.org/show_bug.cgi?id=160813 --- Comment #4 from quach...@duck.com --- I understand your explanations, just as feedback, never reply a request with and? Someone in this world makes an effort to report something and instead of being grateful for that, you trigger a defensive mechanism. I don't know for whom you LibreOffice developers are doing this, but it's no secret that most computers run Windows and if you want to grow your customer base, make the on-boarding from MS Office to LibreOffice as smooth as possible. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 153158] fontconfig alias not respected on SVG import
https://bugs.documentfoundation.org/show_bug.cgi?id=153158 --- Comment #9 from Julien Nabet --- (In reply to Buovjaga from comment #8) > (In reply to Julien Nabet from comment #7) > Appimages are available for 1.3.x: > https://inkscape.org/release/all/gnulinux/appimage/ Thank you for the idea. It's the first time Appimages, works well! :-) (In reply to Julien Nabet from comment #7) > > ... > > If the font is unavailable, its name is still shown in the Text and Font > > tab, but crossed out with a red line. Can you see that? (Using Inkscape > > 1.3.1) > > ... > I use Debian testing package Inkscape 1.2.2 and I see the name but it's not > crossed out with red line. with 1.3.2 Inkscape AppImage, i confirm I see it with crossed out red line. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160757] cant start libre office except in safe mode (Skia / Vulkan)
https://bugs.documentfoundation.org/show_bug.cgi?id=160757 --- Comment #12 from Julien Nabet --- (In reply to colourfuldesu from comment #11) > for the vulkan thingy, idk what's the benefit but it shows as OpenCl in that > LibreOffice\4\cache folder > > https://imgur.com/a/spGUe12 Just for the record, Vulkan is related to "openGL", "openCL" is another unrelated thing. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 140634] calc: date values: problems with change from julian to gregorian calendar, fill functions fail
https://bugs.documentfoundation.org/show_bug.cgi?id=140634 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4699 Status|UNCONFIRMED |NEW --- Comment #5 from Mike Kaganski --- Still repro using Version: 24.2.2.2 (X86_64) / LibreOffice Community Build ID: d56cc158d8a96260b836f100ef4b4ef25d6f1a01 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: default; VCL: win Locale: en-GB (ru_RU); UI: en-GB Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Bug 144699] Use proleptic Gregorian consistently for *all* date formatting and recognition
https://bugs.documentfoundation.org/show_bug.cgi?id=144699 Mike Kaganski changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||0634 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160732] Rename "Navigation" toolbar to clarify its role, avoid confusion, and relate to "Navigate by - Recency"
https://bugs.documentfoundation.org/show_bug.cgi?id=160732 --- Comment #9 from V Stuart Foote --- (In reply to Stéphane Guillou (stragu) from comment #7) > Sounds like "Position History" is the top contender - which makes me think: > do we also want to make the Navigate By dropdown's text consistent with it, > by replacing "Recency" with "Position History"? "Navigate by - position > history" works well. > I think it would make sense and clarify the role. "Recency" makes it sound > like "how recently the object was created". In that list, it's the only > element out of 21 that is about about "things that don't exist anymore". All > other elements are about "what currently exists in the document" (or > session, for Reminders). We better make that extra clear with an > appropriate, consistent label. > "Position History" (16 chars) wouldn't be too long for that Navigate By list > - "Wrong table formula" is already longer (20 chars). No objection, +1 "In for a Penny..." -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160815] Anchor option "To Page" removed from context menu and menu bar (as for bug 135836) now needs documentation adjustment
https://bugs.documentfoundation.org/show_bug.cgi?id=160815 V Stuart Foote changed: What|Removed |Added Component|Writer |Documentation Summary|Anchor option "At Page" |Anchor option "To Page" |missing from context menu |removed from context menu |and menu bar|and menu bar (as for bug ||135836) now needs ||documentation adjustment CC||olivier.hallot@libreoffice. ||org, ||stephane.guillou@libreoffic ||e.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||5836 --- Comment #3 from V Stuart Foote --- The Anchor 'To Page' .uno:SetAnchorToPage remains available to customize as menu, context menu, or TB button. For bug 135836 it was only removed from the menu Format -> Anchor group and corresponding context menu group. It can't be added back at precisely that location (so the built-in Help needs a tweak), but is trivial to continue to use when necessary. So make this against documentation, or it remains a clear dupe of bug 140702 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160757] cant start libre office except in safe mode (Skia / Vulkan)
https://bugs.documentfoundation.org/show_bug.cgi?id=160757 --- Comment #11 from colourfuld...@gmail.com --- for the vulkan thingy, idk what's the benefit but it shows as OpenCl in that LibreOffice\4\cache folder https://imgur.com/a/spGUe12 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 160757] cant start libre office except in safe mode (Skia / Vulkan)
https://bugs.documentfoundation.org/show_bug.cgi?id=160757 --- Comment #10 from colourfuld...@gmail.com --- https://youtu.be/lXYnAcrZVzI I tested a bit, if I disable "use skia for all rendering", I can launch LibreOffice just as if I enable "use skia for all rendering" and "force skia software rendering" but this time 0:20, I cant launch LibreOffice if I just disable skia at all 0:40 then I try to using dgpu then switch to igpu, no change 1：20 I enable force skia through config and LibreOffice can launch so the fix is if I disable skia, it launch. If I enable skia AND force skia, it launch. but I need to do the 2nd solution to make libre launch with disabled skia. somehow if I force enable skia in safe mode, the settings just reverts back that I need to configure it though config file. I dont know how do I make my dgpu RX5500M came up in vulkan mode, I would prefer it to be the other igpu for battery life reasons sorry for the late reply, iam just really lazy in college hahaha -- You are receiving this mail because: You are the assignee for the bug.
[Bug 95347] Store sidebar state (normal, collapsed, hidden) per module
https://bugs.documentfoundation.org/show_bug.cgi?id=95347 --- Comment #9 from David Viner --- This is related to my request added on the link below, which is asking for per-module/app settings for the sidebar as I always use Writer with it showing and Calc with it hidden. https://ask.libreoffice.org/t/do-separate-sidebar-open-close-settings-per-app-exist/105128 David -- You are receiving this mail because: You are the assignee for the bug.
[Bug 156779] TOOLBAR: 'Text formatting' toolbar disappears once you click outside of text box
https://bugs.documentfoundation.org/show_bug.cgi?id=156779 Samuel Mehrbrodt (allotropia) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=87 ||676 -- You are receiving this mail because: You are the assignee for the bug.
