Problem description: When trying to edit a .ppt presentation (even one which was produced by libre) shift-tab on a second level bulleted list indents and switches to an odd bullet. This corresponds to Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/330117 and OpenOffice bug : https://issues.apache.org/ooo/show_bug.cgi?id=99843 Steps to reproduce: 1) Open a shell, type libreoffice 2) You see a libreoffice window asking you what type of document you want, click 'presentation' 3) You now see an empty document with 'Click to add title' and a centred 'Click to add text', on the right there isa series of sections, Master Pages, Layouts, table Design. If 'layouts' isn't already open, click on the >Layouts to open it, 4) Click on the left most layout on the 2nd row - if you hover over it it says 'Title, Content'. When you click the empty document changes so that the 'Click to add text' is now at the top left with a round bullet. 5) Click on 'Click to add title', type 'This is a title' 6) Now click on the 'Click to add text' and and type 'Level 1' hit return 7) Now hit tab and type Level 2 hit return (as you hit tab the bullet changes to a -) 8) type More level 2 and hit return and then Yet more level 2 9) Now go to File->Save as, select a Filter: of Microsoft Powerpoint 97/2000/XP/2003 (.ppt), type a filename (say broken2.ppt) and hit save 10) Convert the 'use Microsoft Powerpoint 97/2000/xp/2003 format' prompt 11) Exit libreoffice (File->Exit, click Discard when it prompts) 12) Now reopen libreoffice (e.g. at the terminal) 13) Use File->Open to open broken2.ppt 14) Click on the L of the 1st line that says Level 2 and then double click, the 'Level 2' is now inverted to show it's highlighted. 15) Hit shift-tab step 15 now shows the bug - Current behavior: the text incorrectly moves to the right and a bullet >> is shown. Expected behavior: it should be moving to the left and the bullet should match the 1st level bullet. Note this happens if you don't go through a .ppt format at any stage. Platform (if different from the browser): Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/535.19 (KHTML, like Gecko) Ubuntu/12.04 Chromium/18.0.1025.168 Chrome/18.0.1025.168 Safari/535.19
I am not sure if this is a misunderstanding. For me it seemed to behave as normal (with LO 4.0.2.2 [Win7 Home, 64bit]). If I press the tabulator key it should move to the right, to the next level with a bullet. Why should it therefore move to the left? Is this maybe a misunderstanding from side?
Note step 15 is asking for 'shift tab' - not plain tab Plain tab goes to the right, Shift-tab should go to the left Indeed shift-tab works fine in most cases, but this case it doesn't work and goes the wrong way.
@Dave: Thank you very much for your hint. I never used this shortcut key and was not aware of it. But I tested it in other presentations and I can confirm if you use Shift Key + Tabulator Key then it moves left, but in this specific case here it moves right. reproducible with LO 4.0.2.2 (Win7 Home, 64bit)
I just tested it in LibreOffice Version 3.6.4.3 (Version ID: 2ef5aff) in Windows, and I can confirm this version and platform is also affected by this bug. My version is in Portuguese (Brazil) language. I know this is not the latest version, there is already the 3.6.6 version in 3.6 branch and that 4.0.2 is already available. I'm downloading the 4.0.2 version and I will test again, but AFAIK this bug was not addressed by this release.
Just installed version 4.0.2 for Windows and confirmed that the bug is still there. Version 4.0.2.2 (Version ID: 4c82dcdd6efcd48b1d8bba66bfe1989deee49c3)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (4.4.1.2 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-03-03
Still present on: libreoffice4.4-4.4.1.2-2.x86_64 (Tested on fedora 21)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Still present in 5.1.2.2 on Ubuntu Xenial (build ID 1:5.1.2-0ubuntu 1) (This isn't a regression - it goes back at least as far as 3.0.1 if you follow into the OOo bug)
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.7 or 5.3.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170522
still present on 5.3.2.1-2.fc26 (Fedora 26)
That is a problem with the old ppt format. For pptx the behavior is correct. Not sure whether developers should repair import/export filter for legacy file formats.
** Please read this message in its entirety before responding ** 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
still present in: Version: 6.1.2.1 Build ID: 6.1.2.1-2.fc29 (Note this was originally reported in OpenOffice in 2009 - it would be great to get it fixed by it's 10th birthday)
Dear Dave Gilbert, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still present in 6.3.2.2, build 6.3.2.2-1.fc31 on Fedora 31
As requested; setting to 'inherited from OOo' based on https://bz.apache.org/ooo/show_bug.cgi?id=99843 which reported it on 3.0.1
I've been chasing this backwards through the filters and I can make the bug go away by commenting out: svdfppt.cxx: PPTStyleSheet::PPTStyleSheet: if ( eNumRuleType == SvxNumRuleType::PRESENTATION_NUMBERING ) aRule.SetLevel( 0, aNumberFormat ); but it's confusing. What I'm seeing is that in the m_pDefaultSheet the mpNuMBuulletItem[Page] ends up having: <aFmts i="0" ptr="0x3709290"> <SvxNumberFormat sPrefix="" sSuffix="" nStart="1" cBullet="bb" <aFmts i="1" ptr="0x3709580"> <SvxNumberFormat sPrefix="" sSuffix="" nStart="1" cBullet="f02d" <aFmts i="2" ptr="0x3709620"> <SvxNumberFormat sPrefix="" sSuffix="" nStart="1" cBullet="2022" <aFmts i="3" ptr="0x37096c0"> <SvxNumberFormat sPrefix="" sSuffix="" nStart="1" cBullet="2013" <aFmts i="4" ptr="0x3709760"> <SvxNumberFormat sPrefix="" sSuffix="" nStart="1" cBullet="bb" <aFmts i="5" ptr="0x3709800"> <SvxNumberFormat sPrefix="" sSuffix="" nStart="1" cBullet="bb" (Same up to 9) so that rule overwrites the 0th number format with the last one loaded; but there's no comment to say why. Note this isn't apparently happening from a file generated from ppt - but I'm not sure why.
I'm now pretty convinced that those two lines are outdated by commit 8a64144fddde61dd050da4cb93b4a7242a495bb2 from 2008 from bz https://bz.apache.org/ooo/show_bug.cgi?id=75927 which changed how outlining worked, so that slot 0 now meant something different.
(And the SetLevel(0 two lines have been there all the way back to 638c)
Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f52932218c5365cbe1635f88d310d9e1189ed182 tdf#49856 Fix level 0 bullet/style on ppt import It will be available in 7.1.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.
Dr. David Alan Gilbert committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f580114e9da5b96a2ba61bbf527e33ab127b2a8d tdf#49856 Add a test It will be available in 7.1.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.