Bug 79904 - Wrong color in a pdf file
Summary: Wrong color in a pdf file
Status: RESOLVED FIXED
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-11 05:13 UTC by Duan Yao
Modified: 2016-03-16 14:23 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
Poppler renders the attached file with an additional light gray area (660.91 KB, text/plain)
2014-06-11 05:13 UTC, Duan Yao
Details

Description Duan Yao 2014-06-11 05:13:35 UTC
Created attachment 100858 [details]
Poppler renders the attached file with an additional light gray area

Poppler renders the attached file with an additional light gray area in the middle of the page. Both pdftocairo and pdftoppm have this issue.

Adobe reader and foxit reader don't, those area should be transparent. 

I build poppler from latest master 1b705331019b155f2138d4b9f5a5bd03ec59193d on ubuntu 14.04. configuration:

Building poppler with support for:
  font configuration: fontconfig
  splash output:      yes
  cairo output:       yes
  qt4 wrapper:        no
  qt5 wrapper:        no
  glib wrapper:       yes
    introspection:    no
  cpp wrapper:        yes
  use gtk-doc:        no
  use libjpeg:        yes
  use libpng:         yes
  use libtiff:        yes
  use zlib:           no
  use libcurl:        no
  use libopenjpeg:    yes
  use cms:            yes
      with lcms2
  command line utils: yes
Comment 1 gaojun1000 2014-08-29 20:22:42 UTC
I ran into a similar problem and solved it by compiling poppler with openjpeg2000.
Comment 2 Duan Yao 2014-08-30 01:13:49 UTC
(In reply to comment #1)
> I ran into a similar problem and solved it by compiling poppler with
> openjpeg2000.
Thanks for the info!
Does poppler on your machine render the attachment correctly?
Is openjpeg2000 same as libopenjpeg? It seems enabled in my poppler.
Comment 3 gaojun1000 2014-09-02 23:50:27 UTC
The problem can be solved by disabling cms (./configure --enable-cms=none), though I don't know why it doesn't work well with cms.
Comment 4 Duan Yao 2014-09-03 02:39:21 UTC
Yes, I had tried without cms, however it caused other severe issues.
Comment 5 Thomas Freitag 2016-03-16 14:23:46 UTC
Fixed in actual version


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.