GNOME Bugzilla – Bug 774567
Zoom level -nan%
Last modified: 2018-05-22 16:53:44 UTC
Created attachment 340025 [details] Screenshot of the opened document Upon opening PDF document, the zoom level is set to nan%, selecting any other exact zoom level sets -nan% (see attached screenshot). Both settings blocks viewing of the document. The fit options and automatic level, sets the zoom to 0% and display the document as expected. Additionally, the zoom in and zoom out options does not work.
I also have the same issue in Ubuntu 16.04 with the default evince from the that version's Ubuntu. Evince version is: 3.18.2 When I was seeking resolution, I've wrote the following help message on evince's irc channel: Ever since I've upgraded to Ubuntu 16.04, I can't change zoom in evince. When I change percentage by hand or choose from the zoom drop-down list, the zoom field changes to "-nan%". When I chose "auto", "by width" or "by document size", the field sets to "0%" value. But any way I change, it doesn't affect document zooming anyhow, except, when the field changes to -nan%, the ducument disappears from the view completely. ctrl+{Mouse wheel}, or ctrl++, ctrl+- also don't help.
I have new findings. This issue has something to do with my current monitor setup and xrandr settings. This bug appears after I run: $ xrandr --output DisplayPort-1-1 --auto --primary --output DisplayPort-1-2 --auto --right-of DisplayPort-1-1 --output DisplayPort-0 --auto --left-of DisplayPort-1-1 --output DVI-0 --auto --left-of DisplayPort-0 Seems like an issue in getting the correct resolution?
Can you post the info of your monitors? like dpi with height etc? that you obtaind with xrandr or other tool.
Sure. The funny thing is, I remember all worked few weeks ago, before I changed the setup slightly and swapped the analog output for the fourth monitor to digital one. $ lspci | grep VGA 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] $ xrandr Screen 0: minimum 320 x 200, current 5120 x 1024, maximum 16384 x 16384 DisplayPort-0 disconnected (normal left inverted right x axis y axis) VGA-0 disconnected (normal left inverted right x axis y axis) DVI-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.02*+ HDMI-2-0 connected 1280x1024+1280+0 338mm x 270mm 1280x1024 60.02*+ DVI-2-1 disconnected VGA-2-1 disconnected DisplayPort-1-1 connected primary 1280x1024+2560+0 338mm x 270mm 1280x1024 60.02*+ DisplayPort-1-2 connected 1280x1024+3840+0 338mm x 270mm 1280x1024 60.02*+ DVI-1-0 disconnected $ xdpyinfo name of display: :0 version number: 11.0 X.Org version: 1.18.4 screen #0: dimensions: 5120x1024 pixels (0x0 millimeters) resolution: -2147483648x-2147483648 dots per inch depths (7): 24, 1, 4, 8, 15, 16, 32
Wow. Thanks for the hint. The bug is solved! The resolution is incorrectly recognized. To get rid of the bug and restore the correct evince zoom function one need to run $ xrandr --dpi 96 Personally, I think this is not an Evince bug.
I think we still need to recognize that the DPI is wrong and then assume the DPI is 96 in evince. But at least we have a workaround. Thanks
(In reply to José Aliste from comment #3) > Can you post the info of your monitors? like dpi with height etc? that you > obtaind with xrandr or other tool. I hope, this is what you need (I just ran xrandr without parameters): Screen 0: minimum 320 x 200, current 4160 x 1024, maximum 16384 x 16384 HDMI-0 disconnected (normal left inverted right x axis y axis) DVI-0 disconnected (normal left inverted right x axis y axis) VGA-0 connected 1440x900+1440+0 (normal left inverted right x axis y axis) 408mm x 255mm 1440x900 59.89 + 74.98* 1280x1024 75.02 60.02 1280x960 60.00 1152x864 75.00 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 75.00 60.32 56.25 640x480 75.00 60.00 720x400 70.08 VGA-1-1 connected 1280x1024+2880+0 376mm x 301mm 1280x1024 60.02*+ 75.02 1280x960 60.00 1280x800 59.81 1152x864 75.00 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 640x480 75.00 72.81 66.67 60.00 720x400 70.08 HDMI-1-1 disconnected DVI-1-0 connected primary 1440x900+0+0 408mm x 255mm 1440x900 59.89*+ 74.98 1280x1024 75.02 60.02 1280x960 60.00 1152x864 75.00 1024x768 75.08 70.07 60.00 832x624 74.55 800x600 75.00 60.32 56.25 640x480 75.00 60.00 720x400 70.08 1280x1024 (0x45) 108.000MHz +HSync +VSync h: width 1280 start 1328 end 1440 total 1688 skew 0 clock 63.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 60.02Hz 1280x1024 (0x46) 135.000MHz +HSync +VSync h: width 1280 start 1296 end 1440 total 1688 skew 0 clock 79.98KHz v: height 1024 start 1025 end 1028 total 1066 clock 75.02Hz 1280x960 (0x47) 108.000MHz +HSync +VSync h: width 1280 start 1376 end 1488 total 1800 skew 0 clock 60.00KHz v: height 960 start 961 end 964 total 1000 clock 60.00Hz 1152x864 (0x49) 108.000MHz +HSync +VSync h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.50KHz v: height 864 start 865 end 868 total 900 clock 75.00Hz 1024x768 (0x4a) 78.800MHz +HSync +VSync h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.06KHz v: height 768 start 769 end 772 total 800 clock 75.08Hz 1024x768 (0x4b) 75.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1328 skew 0 clock 56.48KHz v: height 768 start 771 end 777 total 806 clock 70.07Hz 1024x768 (0x4c) 65.000MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.36KHz v: height 768 start 771 end 777 total 806 clock 60.00Hz 832x624 (0x4d) 57.284MHz -HSync -VSync h: width 832 start 864 end 928 total 1152 skew 0 clock 49.73KHz v: height 624 start 625 end 628 total 667 clock 74.55Hz 800x600 (0x4f) 49.500MHz +HSync +VSync h: width 800 start 816 end 896 total 1056 skew 0 clock 46.88KHz v: height 600 start 601 end 604 total 625 clock 75.00Hz 800x600 (0x50) 40.000MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew 0 clock 37.88KHz v: height 600 start 601 end 605 total 628 clock 60.32Hz 800x600 (0x51) 36.000MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew 0 clock 35.16KHz v: height 600 start 601 end 603 total 625 clock 56.25Hz 640x480 (0x52) 31.500MHz -HSync -VSync h: width 640 start 656 end 720 total 840 skew 0 clock 37.50KHz v: height 480 start 481 end 484 total 500 clock 75.00Hz 640x480 (0x55) 25.200MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew 0 clock 31.50KHz v: height 480 start 490 end 492 total 525 clock 60.00Hz 720x400 (0x56) 28.320MHz -HSync +VSync h: width 720 start 738 end 846 total 900 skew 0 clock 31.47KHz v: height 400 start 412 end 414 total 449 clock 70.08Hz 1440x900 (0x57) 106.500MHz -HSync +VSync h: width 1440 start 1520 end 1672 total 1904 skew 0 clock 55.93KHz v: height 900 start 903 end 909 total 934 clock 59.89Hz 1440x900 (0x58) 136.750MHz -HSync +VSync h: width 1440 start 1536 end 1688 total 1936 skew 0 clock 70.64KHz v: height 900 start 903 end 909 total 942 clock 74.98Hz
(In reply to José Aliste from comment #6) > I think we still need to recognize that the DPI is wrong and then assume the > DPI is 96 in evince. But at least we have a workaround. Thanks Yes, 'xrandr --dpi 96' worked and I agree, that error checking sould be done.
I have the same problem on a VMware guest (negative DPI reported by xdpyinfo and zoom not working in Evince), but I can't fix this with the xrandr workaround. Even though this is not an Evince bug, I think that it should still be handled somehow sensibly, like maybe giving a warning and setting a sensible DPI default value. Thanks!
After some updates, I now get 96x96 dpi in Evince, but still -nan% in Evince. Please let me know how I can help diagnose the problem!
After some investigation, I've found out that this problem for me is due to the interaction between Wayland and Evince in Ubuntu (see https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1733793). When I switch to Xorg, I don't see the problem anymore.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/evince/issues/730.