After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 316101 - Evince's window size, position and ui state is not remembered
Evince's window size, position and ui state is not remembered
Status: RESOLVED FIXED
Product: evince
Classification: Core
Component: general
0.4.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
: 347687 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-09-12 16:39 UTC by Sebastien Bacher
Modified: 2006-07-16 16:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Sebastien Bacher 2005-09-12 16:39:41 UTC 
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=15265

"When i resize evince to fullscreen and close it, i expect it to open fullscreen
again just like Nautilus for example. Window position is also not remembered."
Comment 1 Sergej Kotliar 2005-09-18 11:53:32 UTC 
I can confirm this.
Altering the title to also reflect position.
Comment 2 Sergej Kotliar 2005-09-18 11:55:15 UTC 
*** Bug 316454 has been marked as a duplicate of this bug. ***
Comment 3 Stephen Kennedy 2005-09-19 08:10:14 UTC 
Altering title to reflect Bug 316454
Comment 4 Marco Pesenti Gritti 2005-09-22 13:17:03 UTC 
Window size and ui states are remembered per document, not globally, that's by
design. Though window size remembering was borked and I just fixed it in cvs.
Comment 5 Stephen Kennedy 2005-10-03 10:18:19 UTC 
If there is no "per document" size saved, then the default size
should be the size of the last document. That way the default
has most probability of being the right size.

Is this the case?
Comment 6 Ramon de Ruiter 2005-10-07 10:19:43 UTC 
Will this fix make it into 2.12 at some time?
Comment 7 Ajay Gautam 2006-07-16 16:32:01 UTC 
*** Bug 347687 has been marked as a duplicate of this bug. ***