[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 --- Comment #99 from Commit Notification --- Adam Seskunas committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/005f1547b8e5b37da243320b2eb7a84a47f4c821 tdf#143148 Use pragma once in uibase-app It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 143148] Use pragma once instead of include guards (Episode 2: Endgame)
https://bugs.documentfoundation.org/show_bug.cgi?id=143148 --- Comment #98 from Commit Notification --- Yli875 committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/abbdb9cf2a40132f67cd6e0f2e9ad686ff36798b tdf#143148 Use pragma once instead of include guards It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157001] screen reader NVDA Access Issue in LibreOffice Calc's Organize Template Menu
https://bugs.documentfoundation.org/show_bug.cgi?id=157001 Victor changed: What|Removed |Added Version|7.5.4.2 release |5.2.5.1 release -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157001] New: screen reader NVDA Access Issue in LibreOffice Calc's Organize Template Menu
https://bugs.documentfoundation.org/show_bug.cgi?id=157001 Bug ID: 157001 Summary: screen reader NVDA Access Issue in LibreOffice Calc's Organize Template Menu Product: LibreOffice Version: 7.5.4.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: surfer0...@gmail.com Description: The bug prevents NVDA from accessing the menu options in the Organize Template menu of LibreOffice Calc. This menu allows users to perform actions such as renaming, deleting, and applying templates as default. Steps to Reproduce: 1. Open LibreOffice Calc. 2. Change the column width by navigating to Format > Column > Width. 3. Save the changes by pressing Shift+F11, entering a name for the new template, choosing "My Templates" under Templates - Categories, and clicking Ok. 4. Access the Organize Template menu by pressing Ctrl+Shift+N. 5. Use the Tab key to move to the "My Templates" category combo box. 6. Use the Tab key to move to the list of templates. 7. Select your template and press the Applications key to open the menu. Actual Results: NVDA fails to access the menu, preventing the user from accessing options such as renaming, deleting, and applying as the default template. Expected Results: NVDA have access to the template menu. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.5.4.2 (X86_64) / LibreOffice Community Build ID: 36ccfdc35048b057fd9854c757a8b67ec53977b6 CPU threads: 6; OS: Windows 10.0 Build 19045; UI render: Skia/Vulkan; VCL: win Locale: zh-TW (zh_TW); UI: en-US Calc: threaded NVDA issue: https://github.com/nvaccess/nvda/issues/6908 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 157000] New: sessions -- working sessions (groups of documents you're working on) #2
https://bugs.documentfoundation.org/show_bug.cgi?id=157000
Bug ID: 157000
Summary: sessions -- working sessions (groups of documents
you're working on) #2
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: j...@cspv.hu
hi,
I don't intend to pour duplicates on you...
but this new "feature" (functionality) has many aspects,
and now it comes to your mind because you want to do something (which you can1t
yet), and another time it might be a little different situation and a little
different "something" that you're missing from Writer...
It's like a deja vu :) you had a "day dream" and want to remember...
and go at it from various directions... hoping that now it'll "come back" :)
I'm hoping that I can bring it "back" for a few of us (including myself)
so hence this "series" of attempts at this functionality which I refer to as
sessions...
- - -
What I just did on my PC (based on Linux mint):
I've created another "desktop" now there are 3...
and I've moved my Writer instances ("windows") into these, distributed
based on the work they belong to...
I have 3 "works" -- so to speak -- open...
this is why I added another "desktop"...
so I can "travel" from this one to the other.. depending on which I'd like to
focus on at the very moment...
Linux mint is a very stable system...
and I rarely reboot it...
so these 3 desktops (groups of open application instances / windows)
have the 3 heaps of work not only for a given hour but for a week or so...
... I've written down this situation so you could imagine where the idea for
the "sessions" functionality comes from :)
.
ONE STEP towards this functionality could be:
the "WINDOW" menu... a little addition to it...
There could be a separator "- - - - -" / "_" (or sg)
between the "desktops"...
say, the list goes:
Window 1
w2
w3
w4
w5
w6
.
.
.
w11
it could look like:
window 1
w2
w3
w4
w5
w6
.
.
.
w11
AND that would mean 3 "heaps"...
the 3 desktops...
This could be extremely helpful as right now WRITER doesn't sense where its
windows are... (which desktop)
and when you open a document... sometimes nothing happens...
cause it's already open... "in" / "on" another desktop...
when this happens, it'd be great help to see the open "windows" (which we
already can :)) and the groups' outline, so to speak...
(as I imagine, Writer can have no idea which "desktop" its instances are
"placed" at)
+1
and, as a reminder, it'd be great to get a dialogue when starting Writer:
"open previous session?" -- to which we could reply: YEAS! :)
or/and we could set it in the settings like with firefox:
when starting Writer open previous session / continue from where you left work?
and the graphical "window list", what we see when there's no open document,
could be a great means to distinguish "sessions".. groups of documents that we
would like to open at once...
/// thank you for developing Writer!!! /
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156978] Crash on load of ODT with headings/ToC if Navigator open
https://bugs.documentfoundation.org/show_bug.cgi?id=156978 --- Comment #9 from Commit Notification --- Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/33ae7c12bbdf19b76ced472ca8aed6cf66477bbe tdf#156978 SwNavigator: fix gtk3 crash on treeview get_sensitive It will be available in 24.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156978] Crash on load of ODT with headings/ToC if Navigator open
https://bugs.documentfoundation.org/show_bug.cgi?id=156978 Commit Notification changed: What|Removed |Added Whiteboard||target:24.2.0 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 145217] Very Slow Startup, File Load Operations in LibreOffice 7.2 on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=145217 QA Administrators changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 152775] [Enhancement] Emphasize the entry the mouse pointer is over in the Writer Navigator content tree
https://bugs.documentfoundation.org/show_bug.cgi?id=152775 --- Comment #12 from QA Administrators --- Dear Jim Raykowski, 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 152837] changing date format is not possible
https://bugs.documentfoundation.org/show_bug.cgi?id=152837 --- Comment #4 from QA Administrators --- Dear ibuy1261, 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 151797] Allow setting single data labels on a line chart with no symbols
https://bugs.documentfoundation.org/show_bug.cgi?id=151797 --- Comment #6 from QA Administrators --- Dear Mark C, 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 145217] Very Slow Startup, File Load Operations in LibreOffice 7.2 on Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=145217 --- Comment #10 from QA Administrators --- Dear Gareth Halfacree, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 151796] Microsoft Excel macro goes down a cell at end of Sub. Libreoffice does not unless you modify the code
https://bugs.documentfoundation.org/show_bug.cgi?id=151796 --- Comment #4 from QA Administrators --- Dear Lee, 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 144822] FEATURE REQUEST: Papers templates and add-ons
https://bugs.documentfoundation.org/show_bug.cgi?id=144822 --- Comment #2 from QA Administrators --- Dear Miguel Mayol-Tur, 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 144474] Ods based on model after model change.
https://bugs.documentfoundation.org/show_bug.cgi?id=144474 --- Comment #16 from QA Administrators --- Dear Arnaldo, 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 75509] Incorrect display of digits in default Numeric formatting of a field when language isn't English
https://bugs.documentfoundation.org/show_bug.cgi?id=75509 --- Comment #17 from QA Administrators --- Dear Pleinlouie, 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 74735] FORMATTING: Smart quotes mismatch when using English and Asian languages interexchangebly
https://bugs.documentfoundation.org/show_bug.cgi?id=74735 --- Comment #6 from QA Administrators --- Dear LL, 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 74391] Double byte characters not shown after highlighting single byte characters
https://bugs.documentfoundation.org/show_bug.cgi?id=74391 --- Comment #11 from QA Administrators --- Dear HT, 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 74352] EDITING: drawing object properties changes don't take effect immediately
https://bugs.documentfoundation.org/show_bug.cgi?id=74352 --- 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 74353] EDITING: Drawing object Shift-resize to preserve aspect ratio isn't honored
https://bugs.documentfoundation.org/show_bug.cgi?id=74353 --- Comment #9 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 143900] File selection control cannot be explicitly associated with a label element
https://bugs.documentfoundation.org/show_bug.cgi?id=143900 --- Comment #2 from QA Administrators --- Dear Christophe Strobbe, 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 73888] FORMATTING/UI: when focusing on styles drop down using keyboard shortcut, text should be selected
https://bugs.documentfoundation.org/show_bug.cgi?id=73888 --- Comment #10 from QA Administrators --- Dear LooseSpokes, 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 142728] FILESAVE PPTX Title slide placeholder type changes
https://bugs.documentfoundation.org/show_bug.cgi?id=142728 --- 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.
[Libreoffice-bugs] [Bug 130941] Graphical issue with vectors in LibreOffice Math
https://bugs.documentfoundation.org/show_bug.cgi?id=130941 --- Comment #7 from QA Administrators --- Dear kyle.vivian7, 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 142639] [EMF] ExtSelectClipRng region data coords should be converted between Window and Viewport with MapMode MM_ANISOTROPIC
https://bugs.documentfoundation.org/show_bug.cgi?id=142639 --- Comment #8 from QA Administrators --- Dear Valek Filippov, 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 127214] Base files macros not being able to run through a command line
https://bugs.documentfoundation.org/show_bug.cgi?id=127214 --- Comment #6 from QA Administrators --- Dear Nuno Seixas, 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 117012] Chart dialog opens with severe delay with certain 16 column data
https://bugs.documentfoundation.org/show_bug.cgi?id=117012 --- Comment #6 from QA Administrators --- Dear Buovjaga, 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 117995] Faulty page numbering sequence when using paragraph style page break
https://bugs.documentfoundation.org/show_bug.cgi?id=117995 --- Comment #8 from QA Administrators --- Dear ajlittoz, 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 156999] Writer splitting words or changing them
https://bugs.documentfoundation.org/show_bug.cgi?id=156999 Rod changed: What|Removed |Added CC||cla...@osu.edu --- Comment #1 from Rod --- Created attachment 189236 --> https://bugs.documentfoundation.org/attachment.cgi?id=189236=edit LibreOffice Help About -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156999] New: Writer splitting words or changing them
https://bugs.documentfoundation.org/show_bug.cgi?id=156999 Bug ID: 156999 Summary: Writer splitting words or changing them Product: LibreOffice Version: 7.3.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: cla...@osu.edu Description: I was proofreading a letter I wrote in Writer and found 2 words that Writer seems to have "split" consistently throughout the letter, for example, the name "Pattison" became consistently "Patti son" and "i.e.," became consistently "ire.," When I found the first occurrence, I thought it was my error, but, when I found this consistently throughout the letter, I knew the error was not mine, but that Writer must have changed all occurrences at some point unbeknownst to me. I've used Writer for years and have never seen this happen before. Has this been reported before by anyone? Steps to Reproduce: 1.re-edit letter 2. 3. Actual Results: unable to reproduce problem - do not know what set of circumstances caused it Expected Results: problem not reproduced Reproducible: Couldn't Reproduce User Profile Reset: No Additional Info: see attachment -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156994] Can't have text area shape the same as the drawing object's area shape
https://bugs.documentfoundation.org/show_bug.cgi?id=156994 V Stuart Foote changed: What|Removed |Added Severity|normal |enhancement CC||vsfo...@libreoffice.org --- Comment #3 from V Stuart Foote --- Don't see much utility to an enhancement to bound draw object text boxes with polygon or ellipsoid to match the object shapes. Dev effort aside, it would be a substantial detriment to OOXML and MS Binary file exchange/interoperability. IMHO the status quo suffices and this => WF. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156997] Can't set table (cell) background transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=156997 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- Should be -> enhancement. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156996] Get a pie chart to show percent values on Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=156996 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- You try but there is not your sample file, please attach one. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156989] Cycle Case on a selection of text affects text outside the block
https://bugs.documentfoundation.org/show_bug.cgi?id=156989 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 --- Comment #1 from m.a.riosv --- Please attach a sample file where to reproduce the issue. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156987] LibreOffice calc uses incorrect theme colors and ends up with black on black text
https://bugs.documentfoundation.org/show_bug.cgi?id=156987 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO --- Comment #2 from m.a.riosv --- Please can you paste the information in Menu/Help/About LibreOffice, there is an icon to copy. And test the options in Menu/Tools/Options/Application colors, at the top to selection about dark mode. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156943] Comments on an indented paragraph get indented as well
https://bugs.documentfoundation.org/show_bug.cgi?id=156943 --- Comment #10 from m.a.riosv --- The comments not added with 24.2 are not modified, clearing direct formatting on comment gets it fine. But test adding a new comment, and you can see how a new style 'comment' it's added in styles. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156843] Fields are not highlighted even after their color setting on LO Writer 7.6.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=156843 m.a.riosv changed: What|Removed |Added Resolution|WORKSFORME |NOTABUG --- Comment #8 from m.a.riosv --- It's not a bug, nothing change. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156905] [Regression] Copy and paste formula, now paste value
https://bugs.documentfoundation.org/show_bug.cgi?id=156905 --- Comment #5 from Fran --- (In reply to Óvári from comment #3) > Thank you for your feedback as do not have Windows to see what the behavior > is there. > > The behavior seen on Linux Mint is: > For LO7.5, if I copy the cell, the formula is pasted. > For LO7.6, if I copy the cell, the value is pasted. > > Maybe this is a GNU/Linux only bug? > > Thank you I experience the same problem described in this bug in macOS. In previous versions, when I pasted a formula it was updated with references to cells in the row where the formula was pasted, not the original raw formula. i.e. in row 1, cell B the formula '=*0.8' was converted to '=*0.8' when the cell was pasted in row 2, cell B. This is actually the behavior expected if you were using Calc instead of a Table in Writer. Since I upgraded to 7.6.0.3, the current behavior is to paste the formula 'as is', so I get '=*0.8' when the cell is pasted elsewhere. This breaks my expectation to work with tables with formulas as described in the previous example. Reproducing the steps mentioned in the Description with the attached document, what I observe is not a "Paste value" result, but a "Paste literal formula", which results in the cell containing the '2', as it was the original value given by the copied formula. It seems the formula is being pasted, but the *raw* formula referreing to the original cells. I hope this helps to understand what is going on here. Thank you -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156998] New: When two tables are selected, applying a style will try to insert a new table
https://bugs.documentfoundation.org/show_bug.cgi?id=156998 Bug ID: 156998 Summary: When two tables are selected, applying a style will try to insert a new table Product: LibreOffice Version: 7.5.5.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rafael.palma.l...@gmail.com In Impress, if you select two different tables and try to apply a table style via the Table Design section of the Properties Deck, Impress will try to Insert a new table instead of applying the style to both tables. Steps to reproduce 1) Create a blank Impress document 2) Insert two separate blank tables 3) Select them both 4) Apply a Table Style using the sidebar 5) The Insert Table dialog will open The expected result would be to have the style applied to both tables. System info Version: 7.5.5.2 (X86_64) / LibreOffice Community Build ID: 50(Build:2) CPU threads: 12; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+wayland) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Ubuntu package version: 4:7.5.5-0ubuntu0.23.04.1 Calc: threaded Also reproducible in LO 24.2 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 95347] Store sidebar state (normal, collapsed, hidden) per module
https://bugs.documentfoundation.org/show_bug.cgi?id=95347 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6770 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 128180] Allow each deck to keep its own width in the sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=128180 Stéphane Guillou (stragu) changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6770 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 103459] [META] Sidebar UI and UX bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=103459 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156770 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156770 [Bug 156770] Sidebar doesn't maintain its user fixed size for example after reload the document or the next time it opens. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156770] Sidebar doesn't maintain its user fixed size for example after reload the document or the next time it opens.
https://bugs.documentfoundation.org/show_bug.cgi?id=156770 Stéphane Guillou (stragu) changed: What|Removed |Added Keywords||bibisectRequest, regression Status|UNCONFIRMED |NEW CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=12 ||8180, ||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=95 ||347 OS|Windows (All) |All Version|5.4.3.2 release |7.4.7.2 release Blocks||103459 --- Comment #6 from Stéphane Guillou (stragu) --- Confirmed, the active deck (temporarily) keeps the same width but switching to another resets its width to its minimum. It should persist after a document reload. Tested with: Version: 7.6.0.2 (X86_64) / LibreOffice Community Build ID: 41d6f628ba3f046f16b5fa9fa8db8d4c2ab3b582 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded To be more precise, Steps to Reproduce: 1- Choose > Navigator from side bar 2- Set to maximum width 3- Switch to Styles deck: note that the width matches the Navigator's 4- File > Reload: note that the Styles deck's width hasn't changed 5- Switch to Navigator deck Result: Navigator deck has minimum width. In fact, all others do once you switch. Reproduced in 7.4.7.2 but not in 7.3.7.2, so marking as a regression. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103459 [Bug 103459] [META] Sidebar UI and UX bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156660] Implement "Step Chart" in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=156660 --- Comment #4 from Rafael Lima --- Creating a stepped chart in LO Calc and exporting to Excel won't work, but this time it's not our problem =) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156660] Implement "Step Chart" in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=156660 --- Comment #3 from Rafael Lima --- (In reply to Stéphane Guillou (stragu) from comment #2) > This is already possible when creating a line chart, using the "stepped" > option in the Line Type dropdown. > Marking as "invalid". > (Or are you after something different?) How did I miss that? You're right, this is already possible! Thanks! Fun fact, this is something LO can do, and MS Excel cannot... it's a nightmare to achieve this in Excel. See for instance: https://www.simonsezit.com/article/step-chart-in-excel/ -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156997] New: Can't set table (cell) background transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=156997 Bug ID: 156997 Summary: Can't set table (cell) background transparency Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com When I set the background of a table or a table cell in Impress, there is no option to set the background's transparency; and there should be. I'm not exactly sure what we have in ODF in this respect; here is the pointer: https://docs.oasis-open.org/office/OpenDocument/v1.3/os/part3-schema/OpenDocument-v1.3-os-part3-schema.html#__RefHeading__1416332_253892949 Remembering that in Impress, table styles aren't actual styles (see bug 151264), I'm not quite sure what that means. Be that as it may - transparency for tables should be supported. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154051] Border transparency
https://bugs.documentfoundation.org/show_bug.cgi?id=154051 Eyal Rozenberg changed: What|Removed |Added CC||libreoffice-ux-advise@lists ||.freedesktop.org Keywords||needsUXEval -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=98259 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||156719 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156719 [Bug 156719] Insert menu contains duplicate accelerator hotkey -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156719] Insert menu contains duplicate accelerator hotkey
https://bugs.documentfoundation.org/show_bug.cgi?id=156719 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED CC||stephane.guillou@libreoffic ||e.org Blocks||98259 Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |stephane.guillou@libreoffic |desktop.org |e.org --- Comment #7 from Stéphane Guillou (stragu) --- Per se, having duplicated accelerators is not a bug as the matches can be cycled by using the accelerator again. As you can imagine, 27 items in the menu makes it difficult to find unique accelerators, given that the English alphabet has 26 letters. I would only try to find an alternative if one of the two led to a submenu, or if it contains a character that is not used elsewhere. In this case, we are lucky: looking at a current master build, the menu only has the letters JQUYZ unused. We can use "U" for "Signature Line". It works for Draw, Calc and Impress too. I'll submit a patch. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=98259 [Bug 98259] [META] Keyboard shortcuts and accelerators bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156994] Can't have text area shape the same as the drawing object's area shape
https://bugs.documentfoundation.org/show_bug.cgi?id=156994 --- Comment #2 from Eyal Rozenberg --- (In reply to Regina Henschel from comment #1) Regina, I believe you're approaching this from a problematic perspective, which is over-adherence to MS Office conventions. If MSO has some quirk or bug, or is missing a feature - we should not adopt this flaw as well in the name of compatibility. Certainly, we should probably support MSO-like behavior as an option, and enable it when importing MSO content; but we shouldn't enshrine and enforce such faults. The same goes for this issue. Microsoft decided to only offer rectangular text areas. Ok, they were lazy (or had other priorities). And we kind of got used to it over the years, since that's how things were in MSO. But that's not what the unbiased user would expect: They would (rightly) consider the choice of a rectangle for the text of a shape object to be arbitrary and gratuitous, as they have not indicated they want to limit the text or other content by some rectangular lines cutting through their circle or ellipse. > When you want, that the outline of the shape bounds the text, then use > another type of shape. Note that we're talking about the opposite: The text should fit itself to the shape, not vice versa. Also, I'm not asking for help achieving this effect (for which your suggestion is good advice) - I'm asking for something to be doable without expending any special thought or effort, or at most the minimal amount of a toggle. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156660] Implement "Step Chart" in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=156660 Stéphane Guillou (stragu) changed: What|Removed |Added Resolution|--- |INVALID CC||stephane.guillou@libreoffic ||e.org Status|UNCONFIRMED |RESOLVED Whiteboard| QA:needsComment| --- Comment #2 from Stéphane Guillou (stragu) --- This is already possible when creating a line chart, using the "stepped" option in the Line Type dropdown. Marking as "invalid". (Or are you after something different?) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156994] Can't have text area shape the same as the drawing object's area shape
https://bugs.documentfoundation.org/show_bug.cgi?id=156994 Regina Henschel changed: What|Removed |Added CC||rb.hensc...@t-online.de --- Comment #1 from Regina Henschel --- We can take it as enhancement request. But for me it is a "wontfix". The custom shapes are defined to have very good compatibility to shapes in OOXML and MS binary formats. And there the text area is always rectangular. You can set size and position of the text area and you can rotate the area, but it is always rectangular. When you want, that the outline of the shape bounds the text, then use another type of shape. Legacy rectangles and ovals, polygons and Bézier curves, all have the property "Adjust to contour". Only that its rendering is currently broken, see bug 152906. When you convert a custom shape, e.g. a star, to a polygon or Bézier curve, then do it before you enter the text, otherwise the text will become curves too. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156939] "Fit height to text" is misleading, only regards growing rather than shrinking
https://bugs.documentfoundation.org/show_bug.cgi?id=156939 --- Comment #5 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #4) > The label is easy to understand and we should not change it unless we do the > same with "Fit width to text" and have good reasons to do. But "Fit width to text" acts differently! It _does_ shrink to fit, it doesn't just extend. The current situation is misleading, suggesting symmetry of the semantics regarding the vertical and horizontal axes. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156709] Undo does not update the accessibility sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=156709 Stéphane Guillou (stragu) changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156709] Undo does not update the accessibility sidebar
https://bugs.documentfoundation.org/show_bug.cgi?id=156709 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Keywords||accessibility --- Comment #6 from Stéphane Guillou (stragu) --- Reproduced in: Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 16d43b7c5396d6382926d514dc9ce10b3ce94cba CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156995] Selecting an embedded SVG is extremely slow in Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=156995 Peter Bleszynski changed: What|Removed |Added Hardware|All |x86-64 (AMD64) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156232] Need to ALT-TAB three times to leave Calc window when focus is in Find toolbar (Xfce)
https://bugs.documentfoundation.org/show_bug.cgi?id=156232 Stéphane Guillou (stragu) changed: What|Removed |Added CC||mister...@protonmail.com --- Comment #9 from Stéphane Guillou (stragu) --- *** Bug 156760 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156760] Having a search dialog open makes window keep focus after alt+tab
https://bugs.documentfoundation.org/show_bug.cgi?id=156760 Stéphane Guillou (stragu) changed: What|Removed |Added Whiteboard| QA:needsComment| Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #2 from Stéphane Guillou (stragu) --- Thanks for the report. This issue is already tracked in bug 156232, so I am marking as duplicate. *** This bug has been marked as a duplicate of bug 156232 *** -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 109182] [META] Cell freezing/fixing/locking bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=109182 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||131450 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=131450 [Bug 131450] Frozen rows and columns are ignored when scrolling -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 131450] Frozen rows and columns are ignored when scrolling
https://bugs.documentfoundation.org/show_bug.cgi?id=131450 Stéphane Guillou (stragu) changed: What|Removed |Added CC||stephane.guillou@libreoffic ||e.org Ever confirmed|0 |1 Summary|Fixing cells is ignored |Frozen rows and columns are |when scrolling |ignored when scrolling Blocks||109182 Status|UNCONFIRMED |NEW --- Comment #10 from Stéphane Guillou (stragu) --- Confirmed in current F-Droid APK, version 7.6 alpha1+. Scrolling does not keep frozen cells in view. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109182 [Bug 109182] [META] Cell freezing/fixing/locking bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156996] New: Get a pie chart to show percent values on Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=156996 Bug ID: 156996 Summary: Get a pie chart to show percent values on Calc Product: LibreOffice Version: 7.1.0.0.alpha0+ Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: draco...@gmail.com Description: Selecting “Source format” in “Number Format for Percentage Value” and select “Percent” with “Decimal places” set to 2, nothing changes. On the contrary, when I go back to that “Number Format and Percentage Value” page, the “Source format” tick box is activated again… It's impossible to show 2 or more decimals in pie charts when using percentage. I tried with versions 7.4.5.1 on Debian end with version 7.0.5.2 on Windows. I followed the steps on https://ask.libreoffice.org/t/how-do-i-get-a-pie-chart-to-show-percent-values/38304/3 without success. Steps to Reproduce: 1.Insert a pie chart; 2.Select the diagram inside the box; 3.Insert data labels; 4. With right click, format label data, select “Percent” with “Decimal places” set to 2 and uncheck Source Format, the percentage numbers return without decimal places. Actual Results: The percentage numbers return without decimal places. Expected Results: The percentage numbers with decimal places. Reproducible: Always User Profile Reset: Yes Additional Info: https://ask.libreoffice.org/t/how-do-i-get-a-pie-chart-to-show-percent-values/38304/3. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156995] Selecting an embedded SVG is extremely slow in Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=156995 --- Comment #1 from Peter Bleszynski --- Created attachment 189235 --> https://bugs.documentfoundation.org/attachment.cgi?id=189235=edit example .odp file demonstrating the issue -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 148789] Android Viewer: Not all rows shown for Calc file with 120% zoom in doc settings
https://bugs.documentfoundation.org/show_bug.cgi?id=148789 Stéphane Guillou (stragu) changed: What|Removed |Added Blocks||107923 CC||stephane.guillou@libreoffic ||e.org Whiteboard| QA:needsComment| Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Stéphane Guillou (stragu) --- Reproduced with current APK on F-Droid, 7.6 alpha1+. I can't scroll past row header 1134 and text "foobar 1334". But then, switching apps and going back to LO Viewer, the view refreshes and I can go beyond that (although it doesn't fix the header misalignment). Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107923 [Bug 107923] [META] Zoom issues -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 107923] [META] Zoom issues
https://bugs.documentfoundation.org/show_bug.cgi?id=107923 Stéphane Guillou (stragu) changed: What|Removed |Added Depends on||148789 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=148789 [Bug 148789] Android Viewer: Not all rows shown for Calc file with 120% zoom in doc settings -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156995] New: Selecting an embedded SVG is extremely slow in Linux
https://bugs.documentfoundation.org/show_bug.cgi?id=156995 Bug ID: 156995 Summary: Selecting an embedded SVG is extremely slow in Linux Product: LibreOffice Version: unspecified Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: bleszyn...@gmail.com Description: It may take up to a minute to select an SVG object that consists of many draw:path> elements within content.xml when selecting with the mouse pointer in the document canvas. The selection is immediate when selecting the same object in the Navigator pane. Ubuntu 22.04 and Clear Linux running Gnome and xorg are affected. Possibly other Linuxes are affected as well. Xorg appears to make many kernel memcpy calls while LibreOffice is frozen upon selecting the object. The "slow" SVG object in content.xml follows this syntax: > > TEST > draw:layer="layout" svg:width="20.723cm" svg:height="14.884cm" > svg:x="6.298cm" svg:y="0.026cm" svg:viewBox="0 0 20724 14885" svg:d="..."> > > > draw:layer="layout" svg:width="0.235cm" svg:height="0.19cm" svg:x="6.294cm" > svg:y="0.116cm" svg:viewBox="0 0 236 191" svg:d="..."> > > > > ... repeat the above elements a few hundred times ... > > Steps to Reproduce: On Linux, select an SVG object that consists of many paths in content.xml Actual Results: Selection take a very long time, depending on complexity and number of elements in the group. Expected Results: Selection should be quick Reproducible: Always User Profile Reset: Yes Additional Info: Does not seem to affect Windows -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156921] No "Autofit text to object" for non-textbox drawing objects
https://bugs.documentfoundation.org/show_bug.cgi?id=156921 --- Comment #6 from Eyal Rozenberg --- Bug 156994... that's what it _really_ means for text to fit an object! -- 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 Eyal Rozenberg changed: What|Removed |Added Depends on||156994 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=156994 [Bug 156994] Can't have text area shape the same as the drawing object's area shape -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156921] No "Autofit text to object" for non-textbox drawing objects
https://bugs.documentfoundation.org/show_bug.cgi?id=156921 Eyal Rozenberg changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6994 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156994] Can't have text area shape the same as the drawing object's area shape
https://bugs.documentfoundation.org/show_bug.cgi?id=156994 Eyal Rozenberg changed: What|Removed |Added Keywords||needsUXEval See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||6921 Blocks||108741 CC||libreoffice-ux-advise@lists ||.freedesktop.org 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 156994] New: Can't have text area shape the same as the drawing object's area shape
https://bugs.documentfoundation.org/show_bug.cgi?id=156994 Bug ID: 156994 Summary: Can't have text area shape the same as the drawing object's area shape Product: LibreOffice Version: Inherited From OOo Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: eyalr...@gmx.com Created attachment 189234 --> https://bugs.documentfoundation.org/attachment.cgi?id=189234=edit Example of a rectangular vs shape-fitting text area This bug is about drawing objects such as circles, ellipses, rhomboids, stars, clouds etc. When we type text into such a shape, the text area has a _rectangular_ shape - which is not at all the shape of the object we are trying to fill with text. Now, it's true that _sometimes_, a rectangular for the text area can make sense; but generally - the text area shape should have the same shape as the drawing object (with a margin of course, but that is already configurable). In practice, the ask here is for this to at least be an option: For every relevant drawing shape (e.g. not a line), the user should be able to decide whether they want a rectangular text area or one that fits the object shape. I would even say that the latter should be the default; but if it's at least an option then that would already be a significant improvement. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156993] New: Snap guides are not visible
https://bugs.documentfoundation.org/show_bug.cgi?id=156993 Bug ID: 156993 Summary: Snap guides are not visible Product: LibreOffice Version: 24.2.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Keywords: regression Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rb.hensc...@t-online.de Start Impress. Show Rulers. Make sure for Snap Guides "Display" and "in Front" is on. That is in menu View > Snap Guides. Drag from the ruler to the slide. While you are dragging, the guide is visible. When you release the mouse, the guide becomes invisible. It is still there. When you hover it with the mouse you see the drag arrows. And when you right click in that moment, you get the "Edit Snap Line" dialog. The problem is independent of Skia on or off. I see the error in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 6256d5fe2e7cb1bb002d5fe59527d3a3fbf6963f CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: default; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded It was OK in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: fcbae818b793a9ee97a1b5ddc53902be7a2376f5 CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: en-US (en_US); UI: en-US Calc: CL threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156943] Comments on an indented paragraph get indented as well
https://bugs.documentfoundation.org/show_bug.cgi?id=156943 --- Comment #9 from Nadie Nada Nunca --- Created attachment 189233 --> https://bugs.documentfoundation.org/attachment.cgi?id=189233=edit Bug present in latest nightly build -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156943] Comments on an indented paragraph get indented as well
https://bugs.documentfoundation.org/show_bug.cgi?id=156943 --- Comment #8 from Nadie Nada Nunca --- > The issue is solved for dev version. It's not. See how it looks in the latest nightly build (new attachment). -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156975] loext:theme element is missing although theme colors are used
https://bugs.documentfoundation.org/show_bug.cgi?id=156975 Regina Henschel changed: What|Removed |Added Ever confirmed|0 |1 Assignee|libreoffice-b...@lists.free |rb.hensc...@t-online.de |desktop.org | Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Regina Henschel --- Work is started in https://gerrit.libreoffice.org/c/core/+/156267 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156992] The size of the OLE-frame and the embedded document does not match
https://bugs.documentfoundation.org/show_bug.cgi?id=156992 --- Comment #1 from Kadet --- Created attachment 189232 --> https://bugs.documentfoundation.org/attachment.cgi?id=189232=edit Demo-file Extract files to the desktop. Run the db_with_ref_2.odb file. Open form1. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156992] New: The size of the OLE-frame and the embedded document does not match
https://bugs.documentfoundation.org/show_bug.cgi?id=156992 Bug ID: 156992 Summary: The size of the OLE-frame and the embedded document does not match Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kade...@ya.ru Description: The size of the document embedded in the OLE-frame does not correspond to the size of the frame. The OLE-frame is nested in the Base form. Steps to Reproduce: 1.Extract from the archive db_with_ref_2.zip files and put out on the desktop. 2.Run the db_with_ref_2.odb file 3.Open form1 Actual Results: The Calc document nested in the OLE-frame Object2 does not match the size of the parent OLE-frame. An example is shown in Pic2.jpg . Expected Results: A Calc document nested in an OLE-frame Object2 must be inscribed in an OLE-frame and be the same size with it. Reproducible: Always User Profile Reset: Yes Additional Info: Before LO version 7.5.3, this worked. The sizes of the documents corresponded to each other. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156843] Fields are not highlighted even after their color setting on LO Writer 7.6.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=156843 BogdanB changed: What|Removed |Added Resolution|FIXED |WORKSFORME CC||buzea.bog...@libreoffice.or ||g -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 154271] Adjust view port on auto scroll to maximize the visible area
https://bugs.documentfoundation.org/show_bug.cgi?id=154271 Hossein changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |hoss...@libreoffice.org |desktop.org | Status|NEW |ASSIGNED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156991] The document embedded in the OLE frame does not open
https://bugs.documentfoundation.org/show_bug.cgi?id=156991 --- Comment #1 from Kadet --- Created attachment 189231 --> https://bugs.documentfoundation.org/attachment.cgi?id=189231=edit Demo-file Extract the archive to the desktop. Run the db_with_ref_1.odb file. Open form1. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156991] New: The document embedded in the OLE frame does not open
https://bugs.documentfoundation.org/show_bug.cgi?id=156991 Bug ID: 156991 Summary: The document embedded in the OLE frame does not open Product: LibreOffice Version: 7.5.3.2 release Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Base Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: kade...@ya.ru Description: An existing document that is embedded in an OLE-frame embedded in the Base form does not open. Steps to Reproduce: 1.Extract files from the db_with_ref_1 archive.zip and put on the desktop 2.Run the db_with_ref_1.odb file 3.Open Form1 Actual Results: The rtf.odt document embedded in the OLE frame does not open. There is a puzzle in place of the document. Expected Results: The rtf.odt document embedded in the OLE frame should open and show its contents Reproducible: Always User Profile Reset: Yes Additional Info: Prior to LO version 7.5.3, this function worked well. The documents embedded in the OLE-frame were opened. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156767] [META] Technical Writer (EDITING) Suggested bug fixes, enhancements and features for technical writers.
https://bugs.documentfoundation.org/show_bug.cgi?id=156767 Bug 156767 depends on bug 156843, which changed state. Bug 156843 Summary: Fields are not highlighted even after their color setting on LO Writer 7.6.0.3 https://bugs.documentfoundation.org/show_bug.cgi?id=156843 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156843] Fields are not highlighted even after their color setting on LO Writer 7.6.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=156843 Davide changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #7 from Davide --- View > Field shading enable the shading. I din't find this option so far. The issue is solved. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156942] "Fit width to text" shouldn't default to "extend width to fit whole paragraph on a single line"
https://bugs.documentfoundation.org/show_bug.cgi?id=156942 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #3) > > What you ask for is to change the content of the text box. Could be another > > line wrapping or the text size. > > Correct? No, I'm not asking for a change in the content of the text box. The only question is how wide to make the text box. Options are: 1. Same as what the user set it to. 2. The minimum possible width at which the content fits inside the box (with paragraphs possibly laid out on multiple lines. 3. The minimum possible width at which each paragraph in the content fits onto a single line. As we increase or decrease the width, paragraphs are laid out on more or less lines; that does not mean the content has changed. It is important to note that there are no "lines" in the textbox content. There are _pararagraphs_; and there may be line _breaks_, but not lines. (And this is why the description of functionality in comment #1 is not valid - it presupposes there being lines of known width which need accommodating.) -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156918] "Autofit text" for a textbox is ambiguous phrasing: What is made to fit what?
https://bugs.documentfoundation.org/show_bug.cgi?id=156918 Eyal Rozenberg changed: What|Removed |Added Summary|"Autofit text" is ambiguous |"Autofit text" for a |+ users expect both |textbox is ambiguous |interpretations on the |phrasing: What is made to |context menu|fit what? -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156948] all Sheets have the same scaling settings
https://bugs.documentfoundation.org/show_bug.cgi?id=156948 ady changed: What|Removed |Added Resolution|--- |INVALID Status|NEEDINFO|RESOLVED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156967] CALC: Basic: CSV import macro crashes Calc 7.6.0.3 (worked fine in 7.5)
https://bugs.documentfoundation.org/show_bug.cgi?id=156967 raal changed: What|Removed |Added OS|Windows (All) |All Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC||noelgran...@gmail.com Keywords||bibisected, bisected, ||regression Regression By||Noel Grandin --- Comment #3 from raal --- This seems to have begun at the below commit in bibisect repository/OS linux-64-7.6. Adding Cc: to Noel Grandin ; Could you possibly take a look at this one? Thanks 310675fe06d19ee48ca62bd486fe63c9ec8eed93 is the first bad commit commit 310675fe06d19ee48ca62bd486fe63c9ec8eed93 Author: Jenkins Build User Date: Tue Jan 31 07:07:27 2023 +0100 source sha:ba4191ff0de05334ba32b53a09ad992710f03f9d 146368: osl::Mutex->std::mutex in ImplEventAttacherManager | https://gerrit.libreoffice.org/c/core/+/146368 -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156990] New: Autofit text regressions in impress with LibO 7.6
https://bugs.documentfoundation.org/show_bug.cgi?id=156990 Bug ID: 156990 Summary: Autofit text regressions in impress with LibO 7.6 Product: LibreOffice Version: 7.6.0.3 release Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Impress Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sergio.calleg...@gmail.com Description: The new Autofit-text implementation in LibO 7.6 has some regressions wrt the previous one: 1. If you have a list with bullets, etc in an autofit text box, then the bullets alignment with the text is often lost; 2. The text often does not reach the bottom of the text box. This becomes unpleasant when you have two text boxes side to side and you would like to see their bottoms aligned. Steps to Reproduce: 1. Create a text box in impress. 2. Put a list into it, with bullets 3. Select autofit and reduce the box size 4. create another text box on the side of the previous one 5. put some text into it 6. select autofit 7. reduce the box size so that the bottom of the box is aligned to the bottom of the previous box Actual Results: At point 3, the bullets may lose the alignment with the corresponding text. At point 7, the two boxes get filled differently: the bottom of the text in the two boxes does not align. Expected Results: The bullets should stay aligned with the text and there should be a way to assure that the autofit "fills" the boxex to their bottom. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: PresentationDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156989] Cycle Case on a selection of text affects text outside the block
https://bugs.documentfoundation.org/show_bug.cgi?id=156989 James Craig changed: What|Removed |Added Summary|Cycle Case on a selected|Cycle Case on a selection |block of text affects text |of text affects text |outside the block |outside the block -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156989] Cycle Case on a selected block of text affects text outside the block
https://bugs.documentfoundation.org/show_bug.cgi?id=156989 James Craig changed: What|Removed |Added Summary|Cycle Case on a selected|Cycle Case on a selected |clock of text affects text |block of text affects text |outside the block |outside the block -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156989] New: Cycle Case on a selected clock of text affects text outside the block
https://bugs.documentfoundation.org/show_bug.cgi?id=156989 Bug ID: 156989 Summary: Cycle Case on a selected clock of text affects text outside the block Product: LibreOffice Version: 7.3.7.2 release Hardware: x86-64 (AMD64) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jamespcr...@gmail.com Description: When EDITING: I have selected a block of text on which to cycle case. I cycle the case from lower case to title case to lowercase. Other text in the same paragraph, outside the selection, is affected. Take for example this sentence: "I am a Certified Engineer working on an Important Project that is Really Big." I select the words "Important Project" and apply cycle case to change them to lowercase. The words Certified Engineer and Really Big are also changed. Steps to Reproduce: 1. Create a paragraph with some but not all words in title case 2. Select some but not all of the words in title case 3. Cycle the case of the selection a few times Actual Results: All words of title case in the paragraph are changed Expected Results: Only words in the selection are changed Reproducible: Always User Profile Reset: No Additional Info: Changed the case of the selected text only -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156978] Crash on load of ODT with headings/ToC if Navigator open
https://bugs.documentfoundation.org/show_bug.cgi?id=156978 --- Comment #8 from Jim Raykowski --- Gtk3 doesn't like the get_sensitive call used to determine if a heading visibility in the document layout is different than what is indicated in the Navigator. if (pCnt->IsInvisible() != m_xTreeView->get_sensitive(*xEntry, -1)) I am unsure if it is a gtk3 bug or how get_sensitive is used here. Easy enough to go back to not showing Headings entries when they are not in the document layout instead of greying them out. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156988] New: Find cannot find superscripted or subscripted text
https://bugs.documentfoundation.org/show_bug.cgi?id=156988
Bug ID: 156988
Summary: Find cannot find superscripted or subscripted text
Product: LibreOffice
Version: 7.5.3.2 release
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: Writer
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: will.fried...@gmail.com
Description:
If the Find field is set to Format | Position | Superscript or Subscript,
characters that are superscripted or subscripted are still not found. Note that
setting Attributes | Position doesn't help. If *only* Attributes | Position is
set, then all superscripted *and* subscripted text is found. But if Position
*and* Format | Position | Superscript is set, superscripted text is not found.
Steps to Reproduce:
1. Open a new document.
2. Type a character (let's say "a", without the quotation marks).
3. Set that character to superscript.
4. Open the Find dialog (Ctrl-H).
5. Make sure the Find field is set to No Format.
6. Go to Format | Position, select Superscript, and hit OK.
7. In the Find field, type the character you typed (in our example, "a",
without the quotation marks).
8. Hit Find All, Find Next, or Find Previous. See that "search key not found"
appears.
9. In the Find field, type a period (".", without the quotation marks).
10. Enable regular expressions.
11. Hit Find All, Find Next, or Find Previous; they also say "search key not
found."
Actual Results:
"Search key not found."
Expected Results:
The superscripted or subscripted text matching the search string should appear.
Reproducible: Always
User Profile Reset: No
Additional Info:
Version: 7.5.3.2 (X86_64) / LibreOffice Community
Build ID: 9f56dff12ba03b9acd7730a5a481eea045e468f3
CPU threads: 4; OS: Windows 6.1 Service Pack 1 Build 7601; UI render:
Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156944] LibreOffice does not insert picture from KDE Clipboard INTO table-cell but ABOVE table
https://bugs.documentfoundation.org/show_bug.cgi?id=156944 Andreas Mantke changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156944] LibreOffice does not insert picture from KDE Clipboard INTO table-cell but ABOVE table
https://bugs.documentfoundation.org/show_bug.cgi?id=156944 Andreas Mantke changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156925] Add a Color Scheme switcher to the Basic IDE
https://bugs.documentfoundation.org/show_bug.cgi?id=156925 --- Comment #9 from Rafael Lima --- (In reply to Heiko Tietze from comment #8) > Your Breeze variant is maybe not 100% the same as my colors and I'd like to > change just one value. Feel free to edit the patch and change the color. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156843] Fields are not highlighted even after their color setting on LO Writer 7.6.0.3
https://bugs.documentfoundation.org/show_bug.cgi?id=156843 --- Comment #6 from m.a.riosv --- Created attachment 189230 --> https://bugs.documentfoundation.org/attachment.cgi?id=189230=edit Screenshot with field's shadings. Have you enabled Menu/View/Field shadings. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156987] LibreOffice calc uses incorrect theme colors and ends up with black on black text
https://bugs.documentfoundation.org/show_bug.cgi?id=156987 --- Comment #1 from Mikko Rantalainen --- Created attachment 189229 --> https://bugs.documentfoundation.org/attachment.cgi?id=189229=edit Screenshot of the issue Here's a screenshot of the issue. The black areas are not censored content but the actual UI as rendered with Materia-compact theme on Ubuntu 22.04 LTS. -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156987] New: LibreOffice calc uses incorrect theme colors and ends up with black on black text
https://bugs.documentfoundation.org/show_bug.cgi?id=156987
Bug ID: 156987
Summary: LibreOffice calc uses incorrect theme colors and ends
up with black on black text
Product: LibreOffice
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: graphics stack
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: mikko.rantalai...@gmail.com
I'm using LibreOffice with an user account that has selected GTK theme
"Materia-compact" on Ubuntu 22.04 LTS ("jammy"). This results in (among other
things) the formula entry are in the toolbar getting rendered black-on-black
which obviously makes it completely unusable.
Here are the exact versions I have:
$ apt policy libreoffice-calc
libreoffice-calc:
Installed: 1:7.3.7-0ubuntu0.22.04.3
Candidate: 1:7.3.7-0ubuntu0.22.04.3
$ apt policy materia-gtk-theme
materia-gtk-theme:
Installed: 20210322-1
Candidate: 20210322-1
I've reproduced the issue on multiple computers running Ubuntu 22.04 with
multiple desktop environments and the LibreOffice suite is the only software
that has problems with Materia-compact theme.
Note that Tools – Options ... – LibreOffice – Application Colors view is also
completely unusable with most of the view rendered black-on-black, too.
--
You are receiving this mail because:
You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156972] Python error when inserting page number
https://bugs.documentfoundation.org/show_bug.cgi?id=156972 --- Comment #2 from Werner Tietz --- Cannot reproduce Version 0.0.3 of PageNumberingAddon.oxt (https://gitlab.com/lo_extensions/lo-page-numbering/-/tree/master/LibreOffice/versions/0_0_3 ) works for me, both with Version: 7.4.7.2 / LibreOffice Community Build ID: 40(Build:2) CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Debian package version: 4:7.4.7-1 Calc: threaded and also with: Version: 7.6.0.3 (AARCH64) / LibreOffice Community Build ID: 69edd8b8ebc41d00b4de3915dc82f8f0fc3b6265 CPU threads: 4; OS: Linux 6.1; UI render: default; VCL: gtk3 Locale: de-DE (de_DE.UTF-8); UI: de-DE Flatpak Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
[Libreoffice-bugs] [Bug 156972] Python error when inserting page number
https://bugs.documentfoundation.org/show_bug.cgi?id=156972 --- Comment #1 from Werner Tietz --- Hallo which version of the Addon is installed? … Try https://gitlab.com/lo_extensions/lo-page-numbering/-/tree/master/LibreOffice/versions/0_0_3 -- You are receiving this mail because: You are the assignee for the bug.
