[Bug 1476705] Re: [SOLVED] postscript printer hideously slow in some cases (pdftops)
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, and published to pdf, then you would want to avoid cairo. Or if you used a workflow which ends up with a CMYK pdf. But if everything you do is in sRGB or grayscale, then pdftocairo is fine for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1476705 Title: [SOLVED] postscript printer hideously slow in some cases (pdftops) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1476705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1476705] Re: [SOLVED] postscript printer hideously slow in some cases (pdftops)
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 personal or office documents, all momochrome document and the like. But pdftops is better for more general documents, and therefore makes better sence for the default filter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1476705 Title: [SOLVED] postscript printer hideously slow in some cases (pdftops) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1476705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1476705] Re: postscript printer hideously slow in some cases (pdftops)
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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1476705 Title: postscript printer hideously slow in some cases (pdftops) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1476705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1242321] Re: USB 3.0 Harddrive not recognised
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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1242321 Title: USB 3.0 Harddrive not recognised To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1242321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357920] Re: Xerox Phaser 8560DN reboots as soon as I bring up the Print requester
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. Your description suggests that the printer cannot handle the way cups uses ipp to ask for its capabilities. Perhaps it only supports an older version of ipp? Older versions of cups used snmp to gather some data from networked printers. The move to use ipp instead has value, but is not compatible with all existing printers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357920 Title: Xerox Phaser 8560DN reboots as soon as I bring up the Print requester To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1357920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1357920] Re: Xerox Phaser 8560DN reboots as soon as I bring up the Print requester
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 why the printer did not need to be configured to trigger the access pattern it cannot handle. Till would have a better handle on that part of cups, especially as packaged by ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1357920 Title: Xerox Phaser 8560DN reboots as soon as I bring up the Print requester To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1357920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1317599] Re: Evince doesn't show fi-ligatures in a pdf file
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 and /f_f_l for the f-ligs, whereas the original PS fonts — which predate the current glyph name best practices — used the names /fi, /fl. When rendering a pdf file which uses fonts but does not embed them or embed subsets of them, the renderer needs to find a substitute. If fontconfig is used to find such a substitute, and it returns a font which lacks the glyph names said renderer wants — even if it has the glyphs under a different name — the desired glyph will not get painted. Ideally, renderers would notice that the glyph name they want is unavailable and look for alternate names. Or in the case of a known ligature fall back to the un-ligated glyphs. But that hasn’t been written. The quick fix is to limit font equivilents to those which also have the same glyph naming scheme. Fontconfig did that in commit c6aa4d4bfc, in responce to the freedesktop bug report noted above. Distributions should make the same change in their fontconfig packaging. Distributions should do the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1317599 Title: Evince doesn't show fi-ligatures in a pdf file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-gyre/+bug/1317599/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313865] Re: Bad bignum encoding for curve25519-sha...@libssh.org
*** 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 the correct patch from deb’s package. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1313865 Title: Bad bignum encoding for curve25519-sha...@libssh.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1313865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313865] Re: Bad bignum encoding for curve25519-sha...@libssh.org
*** 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 the correct patch from deb’s package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313865 Title: Bad bignum encoding for curve25519-sha...@libssh.org To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1313865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313865] [NEW] Need to update 6.6p1 to 6.6.1p1
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 identifies itself as openssh 6.6p1or 6.5p1. The patch was posted for the express purpose of providing an easy update for 6.6p1 to avoid this bug. Debian has updated sid to 6.6.1p1, and that should copy over to jessie soon. You can see their git for the details. Both utopic and trusty should get this update quickly. And in trusty itself, not just -updates or -backports; notwithstanding the edit to the reported version it is a bug fix for 6.6p1. Any backports or updates repos which have 6.6p1 also should get the update to 6.6.1p1. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1313865 Title: Need to update 6.6p1 to 6.6.1p1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1313865/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1313865] [NEW] Need to update 6.6p1 to 6.6.1p1
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 identifies itself as openssh 6.6p1or 6.5p1. The patch was posted for the express purpose of providing an easy update for 6.6p1 to avoid this bug. Debian has updated sid to 6.6.1p1, and that should copy over to jessie soon. You can see their git for the details. Both utopic and trusty should get this update quickly. And in trusty itself, not just -updates or -backports; notwithstanding the edit to the reported version it is a bug fix for 6.6p1. Any backports or updates repos which have 6.6p1 also should get the update to 6.6.1p1. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1313865 Title: Need to update 6.6p1 to 6.6.1p1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1313865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1272508] [NEW] will postfix 2.11 be packaged in time for trusty’s freeze
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: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1272508 Title: will postfix 2.11 be packaged in time for trusty’s freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1272508/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1272508] [NEW] will postfix 2.11 be packaged in time for trusty’s freeze
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: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1272508 Title: will postfix 2.11 be packaged in time for trusty’s freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1272508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1258646] [NEW] tzdata upgrade dies, killing apt w/o fixing the tty, when /etc/localtime is protected
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 leaves the tty a mess. Instead, should it be impossible to overwrite the existing /etc/localtime, the script should continue without error. ** Affects: tzdata (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1258646 Title: tzdata upgrade dies, killing apt w/o fixing the tty, when /etc/localtime is protected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1258646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 277404] Re: hp laserjet postscript text print does not print some characters
[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 code for level2 and level3. The significant difference seen in ps generated from the posted example pdf is that xpdf, when generating level3 ps, embeds CID keyed fonts as CID keyed fonts. The question, then, is: do the HP printers have bugs when dealing with CID keyed type42 fonts in PostScript jobs, or is Xpdf’s CID-related PS code buggy? A related question is whether CID keyed type1 fonts also have problems. The test would be to send the printer pstopdf -level3 output of a PDF which has CID keyed cff fonts embedded. (I can generate such a test job, if anyone is interested, but do not have access to a PS printer to test it on.) -- hp laserjet postscript text print does not print some characters https://bugs.launchpad.net/bugs/277404 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
