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 653774 - selecting something from the index changes the scale mode
selecting something from the index changes the scale mode
Status: RESOLVED DUPLICATE of bug 684005
Product: evince
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-06-30 19:33 UTC by Robert Roth
Modified: 2013-02-15 23:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Roth 2011-06-30 19:33:40 UTC 
Forwarded upstream from ubuntu, see https://bugs.launchpad.net/ubuntu/+source/evince/+bug/286218 for more details.

Steps to reproduce:
To reproduce here:

1 Download ubuntu pocket guide from http://www.ubuntupocketguide.com/download_main.html
2 Open file in evince and select a specific zoom level (100%)
3 Open the sidebar and set it to "index" mode (not "thumbnails")
4 Select a chapter from the index

Observe that the zoom level has now been set to "best fit" instead of whatever you selected.
Comment 1 woky 2013-02-15 19:23:59 UTC 
Hello,

I can confirm this very annoying bug by following the steps Robert wrote. 

Initially the document was opened with "Fit Page With". After selecting chapter in index it's set to "Best Fit". Then if you exit Evince, start it again and open mentioned document zoom level is always set to "Best Fit" by default. If you change zoom level it's reset to "Best Fit" when you select anything from index menu.
Comment 2 woky 2013-02-15 19:32:29 UTC 
Sorry, forgot to mention versions.

Evince 3.6.1 (poppler/cairo: 0.20.2)
Running Fedora 18, XFCE 4.10 without Gnome settings daemon running.
Comment 3 Germán Poo-Caamaño 2013-02-15 23:47:02 UTC 

*** This bug has been marked as a duplicate of bug 684005 ***