Created attachment 125086
Reduced test case
Reduced test case. This PDF strokes a single path of one of the boxes in
the original PDF. The original PDF draws the boxes with the fill-stroke
operator "B". I've replaced it with a stroke "S".
To reproduce:
pdftocairo -ps reduced-test-case.pdf
Created attachment 125087
Debug patch
This patch shows the problem is caused by
_cairo_path_fixed_stroke_extents().
If the operation is changed to a fill (change line 259 in the PDF from
"S" to "f") the box appears in the output.
--
You received this bug notification because you are a member
Problem is caused by _cairo_path_fixed_stroke_extents() returning wrong
extents.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1300659
Title:
printed pdf file lacks item boxes
Created attachment 120924
Check in ranges in ByteRange array v2
- renamed isInteger() to isIntOrInt64()
- added and use getIntOrInt64()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
Created attachment 120924
Check in ranges in ByteRange array v2
- renamed isInteger() to isIntOrInt64()
- added and use getIntOrInt64()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
(In reply to Albert Astals Cid from comment #120)
> Ok, good, so Adrian can you commit your patch?
Pushed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
Title:
ubuntu pdf doc
(In reply to Albert Astals Cid from comment #120)
> Ok, good, so Adrian can you commit your patch?
Pushed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
Title:
verify digital
I don't think we need to check if the byte range covers the entire
document. Our job, when verifying the signature, is to use the byte
ranges provided in the signature dictionary. It is up to the pdf
producer to ensure the byte range covers the entire document (excluding
the signature value).
All
(In reply to Andre Guerreiro from comment #105)
> Created attachment 120434 [details] [review]
> Improve robustness of SignatureHandler::validateCertificate
>
> This patch adds additional NULL-checking in
> SignatureHandler::validateCertificate() which avoids segfault for some
> signatures like
Created attachment 120889
Check in ranges in ByteRange array
This is an alternative to the patch in comment 108. It checks all ranges
in the ByteRange array.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
(In reply to Albert Astals Cid from comment #114)
> I'm not very convinced by the naming of
> GBool isInteger() { return type == objInt || type == objInt64; }
> what do you think of
> isIntOrInt64() ?
I prefer a single word instead of isXXXorYYY() but I can appreciate that
isInteger() could
(In reply to Albert Astals Cid from comment #114)
> I'm not very convinced by the naming of
> GBool isInteger() { return type == objInt || type == objInt64; }
> what do you think of
> isIntOrInt64() ?
I prefer a single word instead of isXXXorYYY() but I can appreciate that
isInteger() could
(In reply to Andre Guerreiro from comment #105)
> Created attachment 120434 [details] [review]
> Improve robustness of SignatureHandler::validateCertificate
>
> This patch adds additional NULL-checking in
> SignatureHandler::validateCertificate() which avoids segfault for some
> signatures like
Created attachment 120889
Check in ranges in ByteRange array
This is an alternative to the patch in comment 108. It checks all ranges
in the ByteRange array.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
I don't think we need to check if the byte range covers the entire
document. Our job, when verifying the signature, is to use the byte
ranges provided in the signature dictionary. It is up to the pdf
producer to ensure the byte range covers the entire document (excluding
the signature value).
All
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all
I suggest we change the pdfsig "-c" switch to "-nocert". We can easily
add a single character option if we find it is needed. But we can't get
rid of it if we later regret it.
I'm still waiting for an answer to comment 79.
--
You received this bug notification because you are a member of
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information
(In reply to Andre Guerreiro from comment #100)
> Created attachment 119283 [details] [review]
> Manpage improvement
Pushed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
(In reply to Andre Guerreiro from comment #97)
> Quoting from ISO 32000-1 section 12.8.1:
> "This range should be the entire file, including the signature dictionary
> but excluding the signature value itself (the Contents entry). Other ranges
> may be used but since they do not check for all
(In reply to Albert Astals Cid from comment #96)
> As said please let's not spend too much time on arguing over switch names,
> if you really really want -nocert, just push a patch to the
> signatureHandling branch that switches to it.
Done. I've also added a man page. If any further information
What is the output of "pkg-config --cflags nss"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/740506
Title:
verify digital signatures
Status in Evince:
Confirmed
Status in
What is the output of "pkg-config --cflags nss"?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1085526
Title:
ubuntu pdf doc viewer will not let me sign a document
Status in
(In reply to Markus Kilås from comment #88)
> I found a workaround for my build issue by creating symlinks:
> /usr/include/nspr -> /usr/include/nspr4
> /usr/inclyde/nss -> /usr/include/nss3
Are you using configure or cmake? The nss pkgconfig file should contain
the correct include path.
--
You
(In reply to Markus Kilås from comment #88)
> I found a workaround for my build issue by creating symlinks:
> /usr/include/nspr -> /usr/include/nspr4
> /usr/inclyde/nss -> /usr/include/nss3
Are you using configure or cmake? The nss pkgconfig file should contain
the correct include path.
--
You
I've commit my patch and testcase.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1306846
Title:
Inkscape (using cairo) fails to print thin lines to PDF
Status in libcairo:
Fix
Should be fixed now.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1306846
Title:
Inkscape (using cairo) fails to print thin lines to PDF
Status in libcairo:
Fix Released
Status in
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for
(In reply to Albert Astals Cid from comment #82)
> Honestly i don't think spending much time on discussing the option name
> makes much sense, we just need to document it properly and that's it.
I raised this issue because pdfimages uses -j for jpeg but -png, -jp2,
-jbig2, -tiff, and -ccitt for
(In reply to Martin McDowell from comment #8)
> It has been a year since a last post of this bug but I am still getting this
> problem in October 2015. I have Ubuntu 14.04. The PDF is viewed in the
> default Evince document viewer 3.10.3
The fix is in poppler 0.28 released in Nov 2014.
--
You
(In reply to Albert Astals Cid from comment #70)
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?
This is the only thing left that I think needs fixing before the initial
(In reply to Albert Astals Cid from comment #72)
> > Large file support.
>
> Do you think this should be a blocker for the initial release or something
> we can improve later?
I think it should be included.
--
You received this bug notification because you are a member of Desktop
Packages,
(In reply to Albert Astals Cid from comment #74)
> (In reply to Adrian Johnson from comment #73)
> > (In reply to Albert Astals Cid from comment #72)
> > > > Large file support.
> > >
> > > Do you think this should be a blocker for the initial release
(In reply to Adam Reichold from comment #77)
> Some minor suggestions:
>
> * The naming of BLOCK_SIZE and block_len in hashSignedDataBlock seems
> misleading to me, maybe CHUNK_SIZE and block_len?
>
> * The method hashSignedDataBlock could probably be replaced by a static
> function taking the
(In reply to Albert Astals Cid from comment #72)
> > Large file support.
>
> Do you think this should be a blocker for the initial release or something
> we can improve later?
I think it should be included.
--
You received this bug notification because you are a member of Desktop
Packages,
(In reply to Albert Astals Cid from comment #70)
> So we have two things missing, right?
> * Enabling the use of other keystores
> * The name of the pdfsigverify tool
>
>
> I think the enabling the use of other keystores is important but maybe not
> critical for the first release.
>
> For the
(In reply to Albert Astals Cid from comment #74)
> (In reply to Adrian Johnson from comment #73)
> > (In reply to Albert Astals Cid from comment #72)
> > > > Large file support.
> > >
> > > Do you think this should be a blocker for the initial release
(In reply to Albert Astals Cid from comment #70)
> For the pdfsigverify it seems we kind of agreeed on the compromise to call
> it pdfsig that only does verification right now but in the future may
> suppport signing?
This is the only thing left that I think needs fixing before the initial
+ r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
+ r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
+ r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
According the PDF Reference, the ByteRange array contains pairs of
(offset,length).
Why do we ignore the first
(In reply to Adam Reichold from comment #77)
> Some minor suggestions:
>
> * The naming of BLOCK_SIZE and block_len in hashSignedDataBlock seems
> misleading to me, maybe CHUNK_SIZE and block_len?
>
> * The method hashSignedDataBlock could probably be replaced by a static
> function taking the
(In reply to Albert Astals Cid from comment #70)
> So we have two things missing, right?
> * Enabling the use of other keystores
> * The name of the pdfsigverify tool
>
>
> I think the enabling the use of other keystores is important but maybe not
> critical for the first release.
>
> For the
+ r_values[0] = r2.isInt64() ? r2.getInt64() : r2.getInt();
+ r_values[1] = r3.isInt64() ? r3.getInt64() : r3.getInt();
+ r_values[2] = r4.isInt64() ? r4.getInt64() : r4.getInt();
According the PDF Reference, the ByteRange array contains pairs of
(offset,length).
Why do we ignore the first
(In reply to Andre Guerreiro from comment #63)
> I also thought of adding the feature to pdfinfo but it seems wrong to mix up
> something which performs various computations and relies on external state
> (NSS cert DB) to pdfinfo which just reads metadata from the file itself.
pdfinfo already
(In reply to Andre Guerreiro from comment #63)
> I also thought of adding the feature to pdfinfo but it seems wrong to mix up
> something which performs various computations and relies on external state
> (NSS cert DB) to pdfinfo which just reads metadata from the file itself.
pdfinfo already
Created attachment 118380
Don't cull thin lines on vector backends
The patch didn't work for my test case and broke many other tests.
Attached is a new patch that seems to fix the bug. The patch ensures a
minimum line width when calculating stroke extents on vector backends.
--
You received
Created attachment 118381
cairo test for thin lines
This patch contains a cairo test for thin lines.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1306846
Title:
Inkscape (using
(In reply to Bill Spitzak from comment #13)
> Created attachment 118385 [details]
> attachment-30721-0.html
>
> This seems excessively complex, rather than having the later handler (the
> one turning a non-zero float into a zero fixed) be patched instead. I
> figure it would be correct for all
I don't think NSS should be mandatory. It is not required for rendering
PDFs. configure/cmake should include NSS in the "building poppler with
support for" summary.
> byte_range->arrayGet(1, );
> byte_range->arrayGet(2, );
> byte_range->arrayGet(3, );
>
> unsigned int signed_data_len =
I don't think NSS should be mandatory. It is not required for rendering
PDFs. configure/cmake should include NSS in the "building poppler with
support for" summary.
> byte_range->arrayGet(1, );
> byte_range->arrayGet(2, );
> byte_range->arrayGet(3, );
>
> unsigned int signed_data_len =
I'm not sure that removing this functionality is a good idea. Can't we
just add an option to findText to enable a looser search and leave it to
the front ends to decide if/how to expose this option.
--
You received this bug notification because you are a member of Desktop
Packages, which is
This is a poppler bug. I've attached a patch at
https://bugs.freedesktop.org/show_bug.cgi?id=80719 to fix it.
** Bug watch added: freedesktop.org Bugzilla #80719
https://bugs.freedesktop.org/show_bug.cgi?id=80719
--
You received this bug notification because you are a member of Desktop
This is not really a pdf specific problem. We need to always pass
strokes through to the vector backends no matter how thin. I don't know
the best way to do this as I am not familiar with that code that these
patches modify.
--
You received this bug notification because you are a member of
(In reply to comment #15)
Adrian, does the PostScript part looks good to you?
Looks good.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1242678
Title:
evince cannot render some EPS
Yes, you can replace setpagedevice with pop. It is not clear to me how
your patch is doing this. Something like /setpagedevice { pop } bind
def should work.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
Pushed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1243484
Title:
Incorrect handling of orientation when printing PDF files
Status in Poppler:
Fix Released
Status in
Albert,
Any update on the review/testing of these patches?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1243484
Title:
Incorrect handling of orientation when printing PDF files
Created attachment 92877
0008 ensure there is always a valid page size in the output
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1243484
Title:
Incorrect handling of orientation
(In reply to comment #54)
Are the patches fixing pdftocairo the same way as pdftops so that the PS
output of pdftocairo has everything fixed which was fixed in pdftops?
See the following bug report
https://bugs.linuxfoundation.org/show_bug.cgi?id=1176
The rporter tells that all is OK
Yes it is still an issue. I tested with the daily live image and the bug
is also in trusty.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
https://bugs.launchpad.net/bugs/1226009
Title:
DisplayPort
apport information
** Tags added: apport-collected compiz-0.9 regression reproducible
trusty ubuntu
** Description changed:
I have two Dell U2711 monitors plugged into a HD7750 card. One monitor
is connector via DisplayPort, the other via DVI. If I switch the
monitors off then on again
apport information
** Attachment added: DpkgLog.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946054/+files/DpkgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946053/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946052/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: BootLog.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946051/+files/BootLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: GconfCompiz.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946055/+files/GconfCompiz.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: xserver.outputs.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946071/+files/xserver.outputs.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Xrandr.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946069/+files/Xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: xdpyinfo.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946070/+files/xdpyinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: XorgLogOld.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946068/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: LightdmDisplayLog.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946056/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: ProcCpuinfo.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946060/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Lspci.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946058/+files/Lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: LightdmLog.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946057/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946061/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: ProcModules.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946063/+files/ProcModules.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: UdevDb.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946064/+files/UdevDb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: UnitySupportTest.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946066/+files/UnitySupportTest.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: Lsusb.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946059/+files/Lsusb.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: XorgLog.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946067/+files/XorgLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: UdevLog.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946065/+files/UdevLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
apport information
** Attachment added: ProcInterrupts.txt
https://bugs.launchpad.net/bugs/1226009/+attachment/3946062/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu.
(In reply to comment #51)
Is it not possible to solve our problem without ABI change?
Unfortunately not. But you don't need all the patches to fix the bug you
reported. You can omit 0002 since DSC comments don't affect printing.
0004 can be omitted since that is a cleanup that doesn't affect
Public bug reported:
Patch attached.
** Affects: system-config-printer (Ubuntu)
Importance: Undecided
Status: New
** Patch added: fuji-xerox.diff
https://bugs.launchpad.net/bugs/1265778/+attachment/3939708/+files/fuji-xerox.diff
--
You received this bug notification because
Created attachment 91314
0006 - pdftocairo fixes
Apply origpagesize and crop box changes to pdftocairo to ensure it works
the same way as pdftops.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
Created attachment 91315
0007 cairo clip to crop box
Another crop box fix for cairo.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1243484
Title:
Incorrect handling of orientation
Created attachment 91266
0002 - fix media DSC comments
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1243484
Title:
Incorrect handling of orientation when printing PDF files
Status
(In reply to comment #45)
Are you making the qt-ps-converters do the same too?
It should work. All the changes are internal to the PSOutputDev class. I
tried qt4-demo but it doesn't seem to have a print function.
--
You received this bug notification because you are a member of Desktop
PostScript doesn't support transparency. Cairo always rasterizes content
when it can't be natively represented.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1160894
Title:
SVG to EPS
I have not tried it but I expect those three patches should apply to
1.12.4 or later as not much has changed since then.
I would also recommend applying this patch to improve printing
performance:
http://cgit.freedesktop.org/cairo/commit/?id=266d6e71566ac8c5e360c0b32fb78e23e6a06168
This patch
I have not tried it but I expect those three patches should apply to 1.12.4
or later
That should be 1.12.14 or later.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/968785
Title:
I have not tried it but I expect those three patches should apply to 1.12.4
or later
That should be 1.12.14 or later.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1159452
Title:
I have not tried it but I expect those three patches should apply to
1.12.4 or later as not much has changed since then.
I would also recommend applying this patch to improve printing
performance:
http://cgit.freedesktop.org/cairo/commit/?id=266d6e71566ac8c5e360c0b32fb78e23e6a06168
This patch
Public bug reported:
I have two Dell U2711 monitors plugged into a HD7750 card. One monitor
is connector via DisplayPort, the other via DVI. If I switch the
monitors off then on again the monitor connected via DisplayPort
displays a blank screen. The DVI monitor works correctly. I have to
reboot
I've pushed out a fix to make transparency groups normal groups when the
content is opaque.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1159452
Title:
unable to print entire pdf for
Carlos, could you review the patch.
I don't see the Syntax Error messages. Maybe it depends on the font.
What does pdffonts -subst show?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
Works for me with cairo 1.12. Looks like a cairo bug that has been
fixed.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/710137
Title:
evince badly mis-renders gradients in pdf
I can reproduced the problem with 1.12.2 and 1.12.4. But with master the
bug is fixed.
These three patches are the fix:
http://cgit.freedesktop.org/cairo/commit/?id=cffbdf50ce0117d62d6e157369c60e4a8572fd21
http://cgit.freedesktop.org/cairo/commit/?id=599e78ea2ee146c74fc7ffcee32a055dabbefdda
Testing setpagedevice on my printer it seems that if setpagedevice is
called after printing one side in duplex mode, the next page will not be
on the second side but instead start on a new sheet of paper.
If you want to call setpagedevice on each page to allow pages to be
reordered you could emit
1 - 100 of 109 matches
Mail list logo
