** Changed in: ghostscript (Ubuntu)
Status: Fix Released => New
--
ghostscript's bbox driver gives wrong result
https://bugs.launchpad.net/bugs/160203
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
This bug has reappeared in more recent versions that I have tested in i386 and
AMD64:
8.61.dfsg.1-1ubuntu3
and the one that comes with the beta release of Intrepid:
8.63.dfsg.1-0ubuntu4
I have compiled version 8.63 from the upstream sources, and it does not have
this bug.
The problem is
Here is another PostScript file that shows better the bug. The command "gs
-sDEVICE=bbox -dNOPAUSE -dBATCH example2.ps" gives an empty bounding box, which
is wrong:
GPL Ghostscript SVN PRE-RELEASE 8.61 (2007-08-02)
Copyright (C) 2007 Artifex Software, Inc. All rights reserved.
This software come
Public bug reported:
Ghostscript in Gutsy (and Hardy) gives wrong results for the Bounding Box for
most EPS files I've tried. It used to work fine with gs-gpl in Feisty. One
simple example of the failure is the following (using the example.ps file
attached):
gs -sDEVICE=bbox -dNOPAUSE -dBATC
I have just notice something strange. If in the test file example2.ps I remove
the line that says "%!PS-Adobe-2.0",
the bug appears again: the file (see example3.ps attached) is recognized as
PostScript, but the bounding box is wrong:
> ghostscript -sDEVICE=bbox -dNOPAUSE -dBATCH example3.ps
GP
it because I have lots of figures
in my lecture notes that use ghostscript to calculate the bbox before
they can be converted into PDF and added to
the notes (http://fisica.fe.up.pt/eic0014/fisica2.pdf).
Regards,
Jaime Villate
University of Porto, Portugal
--
ghostscript's bbox d
One more thing. This PS file also gives an error:
%!PS
210 490 moveto 120 60 rlineto -10 10 rlineto -120 -60 rlineto closepath clip
newpath
195 495 moveto 125 65 rlineto -10 10 rlineto -125 -65 rlineto closepath fill
showpage
while this one works fine:
%!PS-Adobe
210 490 moveto 120 60 rlineto -1
Hi ^_Pepe_^,
I've just installed the
linux-backports-modules-wireless-karmic-generic
package and the ath5k phy0: noise... messages still keep popping up in dmesg.
I'm using UNR-karmic on a Toshiba NB100
(Linux 2.6.31-19-generic, Atheros AR5001 Wireless Network Adapter).
Thanks for looking into
Oops, sorry for the noise. I had not realized that you had recommended to use
kernel 2.6.32.
After updating to Linux 2-6-32-020632, I'm getting the ath5k messages less
often, but they still persist:
[ 209.311282] ath5k phy0: noise floor calibration timeout (2462MHz)
[ 220.197227] ath5k phy0: n
Well, in bug #427439 sent me to this bug page, and I'm glad they did
because the fix recommend by ^_Pepe_^ in #20 solved my problem :)
--
ath5k phy0: noise floor calibration *failed* (not *timeout*)
https://bugs.launchpad.net/bugs/435808
You received this bug notification because you are a member
Thanks Florian and linuxcub. I had to do both #2 and #3 to make VPython
work in my Ubuntu 9.10 amd64 system.
--
python-visual seg faults even in simple test cases
https://bugs.launchpad.net/bugs/429015
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
vtk cannot be used in wish8.5. I get the following error:
% package require vtk
couldn't load file "/usr/lib/vtk-5.6/libvtkRenderingTCL.so":
/usr/lib/vtk-5.6/libvtkRenderingTCL.so: undefined symbol:
_Z23vtkTclVoidFuncArgDeletePv
attempt to provide package vtkRenderingTCL 5
12 matches
Mail list logo
