Hi, you've probably been sent here because the bug you filed against Evince and a developer posted a link here since the bug is actually a problem with the PDF library that Evince uses called Poppler. If a bug is identified as being a bug in the PDF backend, Poppler, we need to then file that bug against Poppler at the Free Desktop Gitlab instance.
Search Giblab for similar bugs
If you can't find a similar bug open a new bug against Poppler. If you did find a similar bug make a note in it about your bug and close your bug like in step 6.
- The new bug should contain the original report as well as the comments that are most relative (or just paste them all), plus provide a link back to the Evince bug you are copying from. Here's what it looks like:
- Add the developer's email address who requested the move to the CC list on the new poppler bug.
- Post a link to the new Poppler bug in the original Evince bug
Finally close the Evince bug (or ask an Evince hacker) with the resolution: NOTGNOME
Thanks! The Evince Team really appreciates your time helping us out.
If you get a bug posted in the Evince issue tracker (GNOME Gitlab) that is really a bug with the poppler backend here are you instructions for getting help getting the bug transfered.
Link to this page and ask the reporter to follow these instructions for moving the bug to Poppler. You can copy this:
Hi, this looks like a bug with the PDF backend. Could you please follow these instructions to help get this bug fixed. Thank You. https://wiki.gnome.org/Evince/PopplerBugs#poppler
- Mark bug as NEW if you are able to reproduce it.
- Once the bug has been copied over close it in Gitlab with the label "3. Not GNOME".
Examples of Bugs with Poppler filed against Evince
How to check if a bug belongs to Poppler or Evince
Check out this useful comment about it: https://gitlab.gnome.org/GNOME/evince/-/issues/1517#note_960597