gthumb does not remember maximized window size (should it?)

[Rafał Próchniak]

Gthumb always starts with last non-maximized size even when the window is maximized when I quit. Well, if this is not a bug, let's call it enhancement request...

In Breezy I "hardcoded" the window size manually (ugly, I know) as root in gconf keys and I forgot about it.

But in dapper I noticed exactly the same behavior, and there are probably more apps affected - I had some issues with evolution (pretty random: at first it started "full size", but not maximized, later maximized messing my theme (non-default, so doesn't count), now it seems to be ok), which actually made me report this bug in gthumb.

See probably bugs:
https://launchpad.net/distros/ubuntu/+source/totem/+bug/20561
https://launchpad.net/distros/ubuntu/+source/hal/+bug/17238
https://launchpad.net/distros/ubuntu/+source/serpentine/+bug/33639

On second thought, are there apps that do not require to remember size and position?

Do gconf keys storing window size mean that it is supposed to remember its size and position including maximized state?

[Daniel Holbach (dholbach)]

Thanks for the bug report, that's an issue which is known upstream already: http://bugzilla.gnome.org/show_bug.cgi?id=167050

[Timo Aaltonen (tjaalton)]

from upstream:

Comment #3 from Paolo Bacchilega (gthumb developer, points: 16) 2006-10-23 17:22 UTC [reply]

it's wrong to save and restore the window position, the window manager is responsible of setting window positions.

[Jan Schürmann (visionfactory.net)]

when creating a rule within compiz-config, Gthumb starts nearly maximized but there are always 50px on the right side left...

[zolero (zolinux)]

Hi Jan.

Could you please to provide us with your compiz-config setting rule applied to gtumb to start it maximized? BTW I guess, that the 48-50 pixel wide zone at right, would be the launcher wideness (entire app window will be pushed to right) when Unity is used...

Thanks, Zolero.