Bug 810633

Summary: nautilus ignores window state on first launch
Product: [Fedora] Fedora Reporter: Daniel Belton <danielbelton>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17CC: mclasen, vallimar
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 03:54:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Daniel Belton 2012-04-07 13:28:57 UTC
Description of problem: nautilus ignores the setting of org.gnome.nautilus.window-state on first launch after boot. It always starts maximized no matter what the setting of org.gnome.nautilus.window-state maximized is. 


Version-Release number of selected component (if applicable): nautilus 3.4.0-1


How reproducible: Reboot or restart Gnome shell. Start nautilus. Window comes up maximized instead of how it is set in org.gnome.nautilus.window-state. 


Steps to Reproduce:
1. Reboot
2. Start nautilus
3. Window comes up maximized instead of how set in org.gnome.nautilus.window-state
  
Actual results:

A maximized nautilus window the first time nautilus is opened upon every boot.


Expected results:

For the value set in org.gnome.nautilus.window-state maximized to be honored and the window to be sized according to the value of org.gnome.nautilus.window-state geometry. 

Additional info:

Comment 1 Vallimar 2012-04-13 01:26:43 UTC
I can confirm this issue and it is really very annoying.
Will the slide towards user unfriendliness ever end in gnome-land?

Comment 2 Daniel Belton 2012-04-27 17:17:23 UTC
This appears to be fixed by the latest updates.

I will leave this open for the time being to make certain it is fixed.

Comment 3 Fedora Admin XMLRPC Client 2013-05-09 00:05:08 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Admin XMLRPC Client 2013-05-09 00:07:25 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2013-05-09 00:09:59 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora End Of Life 2013-07-04 00:19:52 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2013-08-01 03:54:28 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.