Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#29693 - [nautilus] doesn't remember window position

Attached to Project: Arch Linux
Opened by Chris (realdarkman) - Tuesday, 01 May 2012, 14:11 GMT
Last edited by Jan Alexander Steffens (heftig) - Saturday, 02 June 2012, 22:09 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Nautilus doesn't remember window position

Additional info:
Kernel 3.3.4-1-ARCH, Xorg 1.12.1-1, xf86-video-ati 6.14.4-2, Gnome 3.4.1-1

Steps to reproduce:
Open nautilus, change window position, close nautilus, open nautilus: window has always same position!
Window size is ok!
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Saturday, 02 June 2012, 22:09 GMT
Reason for closing:  Works for me
Comment by Jeremy M. (jskier) - Wednesday, 09 May 2012, 12:36 GMT
I noticed that in nautilus 3.4.1-2 if I restart X the Nautilus window always starts maximized. However closing and opening a window during the same xsession and it still remembers the previous dimensions. Similar but somewhat different, would the devs like another bug entered?
Comment by Jeremy M. (jskier) - Tuesday, 15 May 2012, 12:32 GMT
The dconf key @ org.gnome.nautilus.window-state.maximized is always checked upon loading a new nautilus instance. Once you open it and un-maximize it behavior is what it should be until you reload nautilus. A quick fix would be to autostart a script like this:

gsettings set org.gnome.nautilus.window-state maximized false

Perhaps this is an upstream issue?
Comment by Jeremy M. (jskier) - Tuesday, 15 May 2012, 15:12 GMT
On another note, this effects both architectures, I'm using 64bit.

Also, today's Nautilus update in the repo did not have an impact on this.
Comment by Jan Alexander Steffens (heftig) - Saturday, 02 June 2012, 13:19 GMT
Can't reproduce. Works fine for me.
Comment by Jeremy M. (jskier) - Saturday, 02 June 2012, 22:02 GMT
Did a refresh and reboot today, seems to have worked it self out a few weeks after originally being entered. Unless the original reporter still has issues, this should close.

Loading...