** Changed in: poppler (Fedora)
Status: Unknown => Fix Released
** Changed in: poppler
Status: Unknown => Fix Released
** Changed in: poppler (Fedora)
Importance: Unknown => Medium
** Changed in: poppler
Importance: Unknown => Medium
--
You received this bug notification be
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: evince (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: poppler (Ubuntu Lucid)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: evince (Ubuntu Lucid)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620751
Title:
Sebastian:
No, not really. Luckily applications with own PostScript interpreters (or where
poppler is not used) are not affected by this problem: example: LibreOffice
(haven't had any problems yet, or I haven't noticed), GIMP, Inkscape, Adobe
Reader.
As I could read from internal forums, that it
> Bump. It seems to me that the fix has been available for some 18
months now, and it's still not fixed in the LTS. Who should I complain
to? (-:
Complaining will not help resolving the fact that people are busy and
that they are bugs over the volunteers working on Ubuntu, you are
welcome to contr
in fact the upstream bug indicates it should be fixed in the current
version so closing the current serie bug and making it affect lucid
** Also affects: evince (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: poppler (Ubuntu Lucid)
Importance: Undecided
Statu
where is the fix available?
** Changed in: evince (Ubuntu)
Status: Confirmed => Invalid
** Changed in: poppler (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Bump. It seems to me that the fix has been available for some 18 months
now, and it's still not fixed in the LTS. Who should I complain to? (-:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620751
T
** Changed in: poppler (Ubuntu)
Status: New => Triaged
** Changed in: poppler (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620751
Title:
dvipdf, evi
It's a shame that ubuntu does not release a fix to this problem yet.
According to fedora/red hat bugzilla, this problem has been fixed there
(FC 12, 13). What's up? 10.04 LTS and upward should have received the
fix awhile back.
--
You received this bug notification because you are a member of Ubu
To circumvent this problem, I used to use pdflatex instead of latex.
However, using pdflatex has its own drawbacks. For example, evince is
not able to work correctly if one compiles latex source file with
figures two or more times with a too short time delay between the
compilations.
--
You recei
There is still no backports push on this fix for lucid. What is the
status? The terminal spam is driving me nuts.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620751
Title:
dvipdf, evince: Illegal
I would just like to add a vote for fixing this in 10.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/620751
Title:
dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
--
ubuntu
** Bug watch added: code.google.com/p/chromium/issues #32347
http://code.google.com/p/chromium/issues/detail?id=32347
** Also affects: poppler via
http://code.google.com/p/chromium/issues/detail?id=32347
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #574
It's an easy fix, as far as I can see. Hopefully the poppler lib will be
updated soon.
** Also affects: poppler (Ubuntu)
Importance: Undecided
Status: New
--
dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
https://bugs.launchpad.net/bugs/620751
You received this bug no
Absolutely agree with Martin. Considering 10.04 LTS is meant to be "Long
Term Support", we would like to get it fixed very soon.
--
dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
https://bugs.launchpad.net/bugs/620751
You received this bug notification because you are a member o
Now I have tested the issue in a LiveCD session of ubuntu 10.10-beta
i386 (Maverick Meerkat) installation. The things work correctly now,
i.e. there is no such a message ("Error: Illegal entry in bfrange...")
which I and the other users had reported above.
Of course, I would be happy to be able to
It looks like a bug in poppler library (i.e., libpoppler5 in Ubuntu 10.4
server edition).
I can also confirm this bug and it is still not fixed as of now (Sept 03
2010). I have found the relevant patch from:
https://bugs.freedesktop.org/show_bug.cgi?id=27728
As this seems affect many users, we wo
** Changed in: evince (Ubuntu)
Status: Incomplete => Confirmed
--
dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
https://bugs.launchpad.net/bugs/620751
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
I get the same error messages when doing the following steps:
1.) downloading a ps-file, for example:
http://www.ctan.org/tex-archive/info/simplified-latex/simplified-intro.ps
2.) Using:
$ ps2pdf simplified-intro.ps
to create a pdf file
3.) Opening the pdf-file with evince:
$ evince simplified-int
I get the same error messages when replacing step 4 by "pdftops sample.pdf":
Error: Illegal entry in bfrange block in ToUnicode CMap
Error: Illegal entry in bfrange block in ToUnicode CMap
Error: Illegal entry in bfrange block in ToUnicode CMap
"xpdf sample.pdf" produces the same error messages a
I get the same error messages from Evince with the same procedure. This
must have been caused by some updates that came in August because before
that I didn't get these messages on the same latex project.
--
dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
https://bugs.launchpad.
Thanks for the positive news. At the moment I do not have any Maverick
installation hence I can not test it right now. In near future I plan to
test it in a LiveCD session (alpha3 or beta version).
--
dvipdf, evince: Illegal entry in bfrange block in ToUnicode CMap
https://bugs.launchpad.net/bugs
looks like it's fixed with Maverick , followed your test case and it's
working fine here with Maverick, may you please test the same and
comment back? thanks in advance.
** Changed in: evince (Ubuntu)
Importance: Undecided => Low
** Changed in: evince (Ubuntu)
Status: New => Incomplete
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/620751/+attachment/1501562/+files/Dependencies.txt
** Attachment added: "KernLog.txt"
https://bugs.launchpad.net/bugs/620751/+attachment/1501563/+files/KernLog.txt
** Attachment added: "RelatedPackageVersions.txt"
26 matches
Mail list logo
