[Bug 33848] gthumb does not remember maximized window size (should it?)

Rafał Próchniak burlap at poczta.onet.pl
Sun Mar 5 23:53:13 UTC 2006


Public bug reported:
https://launchpad.net/malone/bugs/33848

Affects: gthumb (Ubuntu)
       Severity: Normal
       Priority: (none set)
         Status: Unconfirmed

Description:
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?




More information about the desktop-bugs mailing list