Bug 83210 - Full screen bug
Summary: Full screen bug
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: Other Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-28 22:53 UTC by Chris
Modified: 2015-07-18 17:27 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
before running full screen and view all the time that remains after its closure (83.95 KB, image/png)
2014-08-28 22:53 UTC, Chris
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2014-08-28 22:53:29 UTC
Created attachment 105397 [details]
before running full screen and view all the time that remains after its closure

System:
Debian Release 7.6(wheezy)
Kernel Linux 3.2.0-4-amd64
MATE 1.8.1

Description of the problem: 
Libre Office does not return to normal window mode after using full screen 

Steps to Reproduce: 
1 Open the full screen 
2 Close the full screen 
3 When we close and open LibreOffice, sometimes back to normal 
4 Open again full screen 
5 Close the full screen 

Current behavior: 
You can not see the window border, after you exit the full screen display. 

Expected behavior: 
Visible window frame, after you exit the full screen display. 

PS: 
In the file "~ / .config / libreoffice / registrymodifications.xcu" after removing all lines of 
"<prop oor:name="ooSetupFactoryWindowAttributes" oor:op="fuse">" LibreOffice starts normally
Operating System: Debian
Version: 4.1.0.4 release
Comment 1 tommy27 2014-08-29 14:16:27 UTC
thanks for your bug report but keep in mind that the 4.1.0.4 release you are using is obsolete.

you are strongly encouraged to upgrade to current LibO 4.2.6.2 release which is the stable version.

I think that thousands of bugs have been fixed during the 4.1.0 --> 4.2.6 development.

I set status to NEEDINFO.

change it to RESOLVED WORKSFORME if issue is gone after upgrade or revert status to UNCONFIRMED if problem persists.
Comment 2 Chris 2014-08-29 16:14:27 UTC
It works for some versions. I have last 4.2.6.2
Comment 3 tommy27 2014-08-30 12:47:32 UTC
finally, is the bug present in 4.2.6.2 or not?
it it works the status should be RESOLVED
Comment 4 tommy27 2014-09-26 20:24:16 UTC
set status to NEEINFO
please tell if bug is still present with latest 4.2.6.2 or 4.3.2.2 releases
Comment 5 Chris 2014-10-30 10:58:09 UTC
I have the latest updates ( LibreOffice 4.3.2.2.0+, Build ID: 430m0(Build:2) ). Bug still exists.
Comment 6 tommy27 2014-10-30 11:53:45 UTC
Ok, I set back to UNCONFIRMED waiting confirmation by another Linux user.
Comment 7 Chris 2014-10-30 13:37:06 UTC
I created a script to run LibreOffice, but has reopened.

Example run:

bash ./LibreOfficeRun.sh --calc %U

[code]
#!/bin/bash

findFile=`find ~/.config -name "registrymodifications.xcu"`

if [ -e ${findFile} ]
then
	echo `grep -v -w "ooSetupFactoryWindowAttributes" ${findFile}` > ${findFile};
fi

case ${1} in

	"%U")
		screen -S LibreOfficeRun -m -d libreoffice ${1} &
	;;
	*)
		screen -S LibreOfficeRun -m -d libreoffice ${1} ${2} &
	;;

esac
[/code]
Comment 8 Buovjaga 2014-11-15 13:02:27 UTC
Can't reproduce.

Ubuntu 14.10 64-bit Version: 4.4.0.0.alpha2+
Build ID: 5bff4b016c4b44f4123e0e6a4fd4c0c4dc0cfa2d
TinderBox: Linux-rpm_deb-x86_64@46-TDF-dbg, Branch:master, Time: 2014-11-13_00:14:29

Version: 4.3.3.2
Build ID: 430m0(Build:2)
Comment 9 Chris 2014-11-22 18:35:29 UTC
I installed a new system the error is gone. Just discovered that the error occurs when using more than one monitor.
Comment 10 Buovjaga 2014-11-22 19:36:29 UTC
(In reply to Chris from comment #9)
> I installed a new system the error is gone. Just discovered that the error
> occurs when using more than one monitor.

I'm a bit confused: does the error still occur for you, if you plug a second monitor into your new system? If yes, we can keep this open as a multi-monitor issue.
Comment 11 Robinson Tryon (qubit) 2014-11-23 11:41:48 UTC
(In reply to Beluga from comment #10)
> I'm a bit confused: does the error still occur for you, if you plug a second
> monitor into your new system? If yes, we can keep this open as a
> multi-monitor issue.

Status -> NEEDINFO
Comment 12 QA Administrators 2015-06-08 14:29:13 UTC
Dear Bug Submitter,

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/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!

This NEEDINFO Message was generated on: 2015-06-08

Warm Regards,
QA Team
Comment 13 QA Administrators 2015-07-18 17:27:45 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-07-18