Bug 52458 - SLIDESHOW: PPT slide content goes off the bottom of the display, and
Summary: SLIDESHOW: PPT slide content goes off the bottom of the display, and
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.5.4 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-24 19:01 UTC by RealNameIs Ed
Modified: 2013-09-24 02:06 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description RealNameIs Ed 2012-07-24 19:01:19 UTC
PPT slide content goes off the bottom of the display, and some images overlap over text 

Problem description: 

Steps to reproduce:
1. Open a PPT presentation
2. Start a slide show
3. Observe each slide

Current behavior: Some text cannot be seen because it shows it going off the bottom end. Some text gets covered up by images.

Expected behavior: Must see the entire slide as normal, as it would be in Powerpoint.

Platform (if different from the browser): This is on Ubuntu Lucid.
              
Browser: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1

I cannot include a screenshot because the presentation I was viewing cannot be shared.
Comment 1 Rob Snelders 2012-11-29 23:09:41 UTC
Thank you for filing this bug.

Can you please provide a presentation-file where it occures, so we can see what happens.
Comment 2 RealNameIs Ed 2012-11-29 23:46:44 UTC
I will try to make time for this.

bugzilla-daemon@freedesktop.org wrote:

>https://bugs.freedesktop.org/show_bug.cgi?id=52458
>
>Rob Snelders <programming@ertai.nl> changed:
>
>           What    |Removed                     |Added
>----------------------------------------------------------------------------
>             Status|UNCONFIRMED                 |NEEDINFO
>     Ever confirmed|0                           |1
>
>--- Comment #1 from Rob Snelders <programming@ertai.nl> ---
>Thank you for filing this bug.
>
>Can you please provide a presentation-file where it occures, so we can see what
>happens.
>
>-- 
>You are receiving this mail because:
>You reported the bug.
Comment 3 QA Administrators 2013-07-18 06:16:06 UTC
Dear Bug Submitter,

Please read the entire message in its entirety before continuing - also please respond directly to FDO when replying - do not reply via email.

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 4 QA Administrators 2013-09-24 02:06:36 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO