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 736723 - pixman_region32_init_rect: Invalid rectangle passed
pixman_region32_init_rect: Invalid rectangle passed
Status: RESOLVED DUPLICATE of bug 736688
Product: evince
Classification: Core
Component: backends
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-09-16 07:46 UTC by Riccardo Magliocchetti
Modified: 2014-09-16 10:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Riccardo Magliocchetti 2014-09-16 07:46:40 UTC 
When scrolling around page 13 the attached pdf with evince 3.12.2 i get this warning:

 *** BUG ***
In pixman_region32_init_rect: Invalid rectangle passed
Set a breakpoint on '_pixman_log_error' to debug

so here's the stacktrace:

+ Trace 234096

  • #0 _pixman_log_error
    at ../../pixman/pixman-utils.c line 317
  • #1 pixman_region32_init_rect
    at ../../pixman/pixman-region.c line 389
  • #2 INT_cairo_region_union_rectangle
    at /build/cairo-t1d7nl/cairo-1.12.16/src/cairo-region.c line 709
  • #3 ??
    from /usr/lib/evince/4/backends/libpdfdocument.so
  • #4 ??
    from /usr/lib/evince/4/backends/libpdfdocument.so
  • #5 ev_document_text_get_text_mapping
    from /usr/lib/libevdocument3.so.4
  • #6 ??
    from /usr/lib/libevview3.so.3
  • #7 ev_job_run
    from /usr/lib/libevview3.so.3
  • #8 ??
    from /usr/lib/libevview3.so.3
  • #9 ??
    from /lib/i386-linux-gnu/libglib-2.0.so.0
  • #10 start_thread
    at pthread_create.c line 309
  • #11 clone
    at ../sysdeps/unix/sysv/linux/i386/clone.S line 129 

The bug was originally filed in pixman, did a quick visit in poppler and it's here.
https://bugs.freedesktop.org/show_bug.cgi?id=82898
Comment 1 José Aliste 2014-09-16 10:19:51 UTC 

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