[I posted this to the poppler bug, but it may be of interest here, too.
-JimC]
The reason the level3 ghostscript generates does not cause the problem
is that ghostscript’s level3 is essentially the same as its level2; only
the name of the procset is different.
Xpdf, OTOH, does generate different
The bug is in fontconfig.
Fontconfig added the Gyre font names to the list of suitable
replacements for the base PostScript fonts because the shapes and
metrics are compatible.
What they didn’t notice (until the bug reports started) is that the Gyre
authors use the names /f_i, /f_l, /f_f, /f_f_i
Public bug reported:
A patch for 6.6p1 was posted on the openssh list fixing a bug in the
25519 negotiation and changing the reported version to 6.6.1p1.
Future versions of openssh, version 6.6.1p1 itself, and other ssh
software, such as libssh, will refuse to speak 25519 to anything which
identi
pdftops and pdftocairo are both from poppler.
pdftops is based on the original xpdf code and does not use cairo at
all.
modern cairo tries to limit the size of tranparency groups to just where
it is needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
pdftocairo is limited by the fact that cairo only handles sRGB.
It is therefore unsuitable any time color is important, eg if the pdf
uses cmyk or named colors or icc profiles, et cetera.
It is fine for printing most web pages, since the browser likely also is
limited to sRGB.
And for simple per
Gimp is also, for now, limited to srgb, so anything coming from gimp
will work fine with cairo.
And, for a postscript printer, jpegs should be converted directly to ps,
not via pdf, so that wouldn't matter either.
But if you used a workflow which used, say, AdobeRGB as the colour
working space, a
This is still present in vivid.
Switching to the performance govenor, removing the drive and re-adding
it worked around the bug.
Something must be blocking power to the xhci when the cpu is saving
power...?
This is also present on non-Ubuntu systems, including ones running
Linus’ latest kernels.
Public bug reported:
When /etc/localtime is protected from manipulation, such as with the
immutable flag — something which is often required when leasing
virtuals, to keep the vendors’ frameworks from screwing with the
filesystem — an update to tzdata will crap out, killing dpkg and apt,
which lea
*** This bug is a duplicate of bug 1310781 ***
https://bugs.launchpad.net/bugs/1310781
I missed the earlier report.
I went from memory on the package version number; ssh -V reports 6.6.1p1
but as you found dpkg says 1:6.6p1-4.
I hope that helps the case for getting it into trusty.
That is t
The cups log shows that you configured the printer as an IPP printer.
(Or that something did so for you.)
Try configuring it as a socket printer (sending the postscript to port
9100).
You may need to use the printer’s web interface or control panel to
enable port9100 if you have disabled it.
You
Ah. I didn’t intially read every comment.
I suspect that the method cups now uses to discover network attached printers
is what triggers the crash/reboot.
It will ipp-query any it finds which advertise ipp capability in lieu of
requiring PPD files to specify the printer’s capabilities. That is
Public bug reported:
It was released more than a week ago, and I see that the import freeze
is less than a fortnight away.
2.11’s benefits are significant enough that it SHOULD be included, even
if it doesn’t make sid or jessie by then.
Will it be?
** Affects: postfix (Ubuntu)
Importance:
12 matches
Mail list logo
