Bug 2327479 - evince still doesn't behave correctly in presentation mode on hidpi display
Summary: evince still doesn't behave correctly in presentation mode on hidpi display
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evince
Version: 42
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-19 21:21 UTC by jan p. springer
Modified: 2025-05-07 03:21 UTC (History)
6 users (show)

Fixed In Version: evince-48.0-2.fc42
Clone Of:
Environment:
Last Closed: 2025-05-07 03:21:35 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
evince -s <some>.pdf on 4k display with 150% scale (78.85 KB, image/png)
2024-11-19 21:21 UTC, jan p. springer
no flags Details
okular <some>.pdf on the same 4k display with 150% scale (98.54 KB, image/png)
2024-11-19 21:21 UTC, jan p. springer
no flags Details

Description jan p. springer 2024-11-19 21:21:00 UTC
Created attachment 2058770 [details]
evince -s <some>.pdf on 4k display with 150% scale

Description of problem:

evince in presentation mode on hidpi display (again!) doesn't show content on the full screen; instead a very tiny canvas is displayed; this is a regression of something thatw as fixed in f40 right before f41 was released!

Version-Release number of selected component (if applicable):

evince-46.3.1-2.fc41.x86_64

How reproducible:

always

Steps to Reproduce:
1. hdpi display with scale other than 100%
2. evince -s <some>.pdf
3. 

Actual results:

displayed .pdf content much, much smaller than display canvas

Expected results:

displayed .pdf content extends to either edge of display canvas

Additional info:

Comment 1 jan p. springer 2024-11-19 21:21:57 UTC
Created attachment 2058771 [details]
okular <some>.pdf on the same 4k display with 150% scale

Comment 2 jan p. springer 2025-02-14 16:49:38 UTC
so, this is not going to be fixed, soon? at all?

Comment 3 Marek Kašík 2025-02-17 09:46:58 UTC
Hi Jan,

I'm sorry for the delay. I'll have a look at this this week.

Comment 4 Marek Kašík 2025-02-20 15:53:21 UTC
Most of my time was consumed by poppler update this week. I'll continue on this next week.

Comment 5 Marek Kašík 2025-02-24 15:33:56 UTC
Hi,

I had a look at this and it seems that we need to set correct scale_factor in ev_view_presentation_update_monitor_geometry() but for this we need the value of fractional scaling which is not easy to get in gtk3. I've posted my findings in https://gitlab.gnome.org/GNOME/evince/-/issues/1600 and will see whether upstream agrees with me and whether they know a way to obtain the value.

Comment 6 jan p. springer 2025-05-02 23:59:41 UTC
(In reply to Marek Kašík from comment #5)
any update/progress on this?

Comment 7 Fedora Update System 2025-05-05 09:59:44 UTC
FEDORA-2025-1f14529925 (evince-48.0-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-1f14529925

Comment 8 Marek Kašík 2025-05-05 10:04:17 UTC
Hi Jan, thank you for reminding me this bug.
Nelson has fixed this 1 week ago for Fedora 42 and I can confirm that the issue has been fixed on my system. I've created updates for Fedora 42 and Fedora 43 with the fix.

Regards

Comment 9 Fedora Update System 2025-05-06 03:33:40 UTC
FEDORA-2025-1f14529925 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-1f14529925`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-1f14529925

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-05-07 03:21:35 UTC
FEDORA-2025-1f14529925 (evince-48.0-2.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.