Bug 54690 - SLIDESHOW: Gnome-Shell top-bar on top of slideshow
Summary: SLIDESHOW: Gnome-Shell top-bar on top of slideshow
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
3.6.3.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-09 14:50 UTC by Florian Monfort
Modified: 2015-02-11 19:52 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments
A screenshot that says all about the problem. (319.04 KB, image/png)
2012-09-09 14:50 UTC, Florian Monfort
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Monfort 2012-09-09 14:50:35 UTC
Created attachment 66881 [details]
A screenshot that says all about the problem.

Problem description: 

Steps to reproduce:
1. Open a presentation in Impress
2. Press F5 to launch Slide Show mode

Current behavior:

The slideshow launches, but Gnome-Shell's top bar stays on top of it.

Expected behavior:

The top bar should be hidden in order to be in complete fullscreen mode.

Platform (if different from the browser): 
              
Browser: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0

Also using Fedora 17, version 3.6.1 downloaded from libreoffice.org
Comment 1 Alexander Hunziker 2012-11-29 22:42:02 UTC
Confirm this on Arch Linux
Comment 2 QA Administrators 2015-01-05 17:51:05 UTC
** 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.3.5 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
Comment 3 Buovjaga 2015-01-22 06:26:44 UTC
Could not reproduce with Scientific Linux 7 64-bit, Gnome 3.8.4, LibO 4.1.4.2 (default).
Florian: do you still have the problem with a newer Gnome & LibO?

Setting to NEEDINFO.
Comment 4 QA Administrators 2015-02-11 19:52:18 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
Message generated on: 2015-02-11