GNOME Bugzilla – Bug 792813
Evince always opens in wrong size even though the settings are saved as default
Last modified: 2018-02-21 21:32:38 UTC
Whenever evince is opened, it opens in a window that is bigger than the size of the screen - as reported in Bug 504438. The bug is unfortunately closed as incomplete but since evince offers the opportunity to save the current settings as default, I would say this is a concrete bug in that the settings are not saved / handled correctly. I my point of view the size is a setting as well and if I tell the program to save them I also expect those to be restored correctly whenever a new window is opened. On the other hand, if the size of the window is specific to the opened document and should not be treated as a "setting" but merely as a document specific attribute, it is also a bug because when I open a document, close it and reopen it in another session, the window is too big again. As mentioned in Bug 504438 this is very annoying and when working with multiple PDF documents again and again, this leads to a noticeable waste of time. Thank you for providing such a good PDF viewer and for taking your time to investigate in bugs.
Take any document you have opened and have changed the window size, and run: $ gio info that_file | grep evince what is the output?
Thanks for the quick response! $ gio info /home/david/...pdf | grep evince metadata::evince::author: David metadata::evince::continuous: 1 metadata::evince::dual-page: 0 metadata::evince::dual-page-odd-left: 0 metadata::evince::fullscreen: 0 metadata::evince::inverted-colors: 0 metadata::evince::page: 12 metadata::evince::sidebar_page: links metadata::evince::sidebar_size: 293 metadata::evince::sidebar_visibility: 1 metadata::evince::sizing_mode: free metadata::evince::title: Diagnosis System metadata::evince::window_height: 1487 metadata::evince::window_maximized: 0 metadata::evince::window_width: 2503 metadata::evince::window_x: 3584 metadata::evince::window_y: -19 metadata::evince::zoom: 1.4674819163389952
*** This bug has been marked as a duplicate of bug 783242 ***