Bug 1938506 - Evince EPS files load very pixelated until file is reloaded
Summary: Evince EPS files load very pixelated until file is reloaded
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libspectre
Version: 35
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Marek Kašík
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-14 01:46 UTC by Karl
Modified: 2021-12-12 01:05 UTC (History)
9 users (show)

Fixed In Version: libspectre-0.2.9-4.fc34 libspectre-0.2.9-5.fc35 libspectre-0.2.9-5.fc36
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 02:06:20 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
EPS image that reproduces the problem on two different Fedora versions (9.34 KB, image/x-eps)
2021-03-25 14:29 UTC, Karl
no flags Details

Description Karl 2021-03-14 01:46:55 UTC
Description of problem:
Loading EPS files (e.g., as produced by Grace) result in very pixelated images. The images resolve to "normal" resolution if CTRL-R is used to reload the file.

Version-Release number of selected component (if applicable):
evince-3.38.2-2.fc33.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open EPS file in evince

Actual results:
Very pixelated image

Expected results:
High-resolution (infinite-resolution?) image.

Additional info:
Pressing CTRL+R to reload the image works around the problem.

Comment 1 Marek Kašík 2021-03-15 10:58:03 UTC
Hi,

could you attach an EPS file on which you see the issue?
Could it be that it just take too long to evince to render the EPS? (Could you watch "top" during the time when the EPS is pixelated?)
Does it happen only when zooming or straight after you open the file?

Comment 2 Karl 2021-03-24 18:19:09 UTC
Here's an example that reproduces it for me on Evince 3.36.9 and 3.38.2.

I now realize that it doesn't happen every time: sometimes, I can load the file once, and it's fine. I can then re-open it a few seconds later and it's pixellated. Sometimes, reloading instantly fixes it, other times it takes a few reloads to do it.

It happens right after you open the file (or after reloading with CTRL+R). It can also be triggered by zooming, but that's not how I first saw it.

It also persists with no processor or abnormal memory usage during the pixellated periods.

Comment 3 Karl 2021-03-25 14:29:22 UTC
Created attachment 1766336 [details]
EPS image that reproduces the problem on two different Fedora versions

It doesn't happen every single time; hit reload a few times if it looks normal.

Comment 4 Ben Cotton 2021-11-04 14:51:47 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Ben Cotton 2021-11-04 15:50:15 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 6 Marek Kašík 2021-11-26 12:28:18 UTC
Hi, I see the issue on Fedora 35 so I'm reassigning it there.

Comment 7 Karl 2021-11-28 21:06:47 UTC
Changed version to 35 in response to comment #6.

Comment 8 Marek Kašík 2021-11-29 08:43:09 UTC
(In reply to Karl from comment #7)
> Changed version to 35 in response to comment #6.

Thanks, I forgot to switch it there.

Comment 9 Marek Kašík 2021-11-29 15:45:27 UTC
Hi,

I had a look at this issue and it seems that there was wrong alignment set for rendering of postscript. I've proposed an upstream fix at https://gitlab.freedesktop.org/libspectre/libspectre/-/merge_requests/37.
Let's wait for upstream's opinion on it.

Comment 10 Marek Kašík 2021-12-03 13:36:30 UTC
Upstream accepted the fix so I've pushed it to Fedora.

Comment 11 Fedora Update System 2021-12-03 13:40:56 UTC
FEDORA-2021-02bc8c126e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-02bc8c126e

Comment 12 Fedora Update System 2021-12-03 13:40:56 UTC
FEDORA-2021-f59e75c04e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f59e75c04e

Comment 13 Fedora Update System 2021-12-04 01:23:48 UTC
FEDORA-2021-f59e75c04e has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f59e75c04e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f59e75c04e

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

Comment 14 Fedora Update System 2021-12-04 02:16:59 UTC
FEDORA-2021-02bc8c126e has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-02bc8c126e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-02bc8c126e

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

Comment 15 Fedora Update System 2021-12-07 02:06:20 UTC
FEDORA-2021-f59e75c04e has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2021-12-12 01:05:05 UTC
FEDORA-2021-02bc8c126e has been pushed to the Fedora 34 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.