[Bug 1449875] [NEW] ghostscript fails on some EPS files
Public bug reported: On Ubuntu 15.04, running in the cloud, I issue to following command to find the Bounding Box on the attached EPS. When I download the ghostscript binary from ghostscript.com or try the same on my FreeBSD server, it works just fine. Here's the command to reproduce: $ gs -q -sDEVICE=bbox -dNOPAUSE -dBATCH -dSAFER -dEPSCrop -r300 broken- on-ubuntu-1504.eps The expected output: %%BoundingBox: 87 81 1515 1510 %%HiResBoundingBox: 87.840941 81.63 1514.790058 1509.385370 The output on Ubuntu 15.04: Error: /undefinedresource in resourcestatus Operand stack: false ct_StyleDicts --dict:0/4(L)-- Adobe-Japan1 --dict:0/4(L)-- Serif HeiseiMin-W3-83pv-RKSJ-H Font HeiseiMin-W3 CIDFont Execution stack: %interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1967 1 3 %oparray_pop 1967 1 3 %oparray_pop 1966 1 3 %oparray_pop --nostringval-- 1950 1 3 %oparray_pop 1836 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- 1915 10 9 %oparray_pop Dictionary stack: --dict:1183/1684(ro)(G)-- --dict:0/20(G)-- --dict:87/200(L)-- --dict:57/75(L)-- --dict:2/10(L)-- --dict:39/70(L)-- --dict:0/4(L)-- --dict:0/4(L)-- --dict:20/27(ro)(G)-- --dict:20/26(ro)(G)-- Current allocation mode is local Last OS error: No such file or directory GPL Ghostscript 9.15: Unrecoverable error, exit code 1 ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Attachment added: This EPS shows the problem in the Ghostscript package https://bugs.launchpad.net/bugs/1449875/+attachment/4387258/+files/broken-on-ubuntu-1504.eps -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1449875 Title: ghostscript fails on some EPS files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1449875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287726] Re: Wrong evaluation whether json is valid or not
I cannot specify it further, since it's our own API that communicates via JSON that broke, due to php-json in Ubuntu not conforming to the JSON standard. Time will tell how many will get hit by this bug. Might be zero, might be thousands. Fact of the matter is still that it accepts JSON input that is not valid JSON according to the JSON standard. I see my two options, and I can certainly understand your stance. We're not able to fix this with the resources we have, and convincing Debian to take a different legal stance is a holy war that I cannot win. so my only option is: 3) Move all servers that use JSON away from Ubuntu and on to something with a JSON standard conforming php-json. Thanks for your time! P.S Will this bug stay open until it's maybe fixed some day? Then I know when I can consider using Ubuntu again. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1287726] Re: Wrong evaluation whether json is valid or not
I cannot specify it further, since it's our own API that communicates via JSON that broke, due to php-json in Ubuntu not conforming to the JSON standard. Time will tell how many will get hit by this bug. Might be zero, might be thousands. Fact of the matter is still that it accepts JSON input that is not valid JSON according to the JSON standard. I see my two options, and I can certainly understand your stance. We're not able to fix this with the resources we have, and convincing Debian to take a different legal stance is a holy war that I cannot win. so my only option is: 3) Move all servers that use JSON away from Ubuntu and on to something with a JSON standard conforming php-json. Thanks for your time! P.S Will this bug stay open until it's maybe fixed some day? Then I know when I can consider using Ubuntu again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287726] Re: Wrong evaluation whether json is valid or not
This also means, that unless the Ubuntu maintainer fixes it either way, then php-json has a rather important change in behaviour between 12.04 LTS and 14.04 LTS. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1287726] Re: Wrong evaluation whether json is valid or not
So the upstream json-c developers don't consider this a bug: Oh, I see. You want json-c to validate that the input being parsed actually is UTF-8. While that might seem reasonable to do at first glance, json-c has historically supported something closer to exact, uninterpreted bytes for strings rather than strict characters, and unconditionally changing this now will be a significant change. Although not strictly to the spec, in many cases I see a value in being able to handle arbitrary data. This is also in conflict to efforts to support even less string-like data as mentioned in Issue#108. Given this, and the fact that performing the additional validation will likely add more overhead to the parsing, any checks to ensure that strings only contain valid UTF-8 sequences would need to be explicitly requested, perhaps by setting the JSON_TOKENER_STRICT flag. Do you happen to have a patch to cause this validation to be done? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1287726] Re: Wrong evaluation whether json is valid or not
Problem is that the old php-json package conforms to the json standard, and the new one does not. If someone went through the effort (we do not have the resources, unfortunately) to make json-c conform to the json standard with said flag, then yes - you could simply compile the package with that flag enabled, and all would be good. The impact of the bug? Json is used all over the place for many years, since it's a very good lightweight format for exchanging data. All of the services provided on a Ubuntu system will potentially break, since it does not conform to the json standard that everyone else does. We had to switch our servers that was running Ubuntu since 2010 to NetBSD to get a modern PHP with proper json handling. Our unit tests broke immediately when we switched to Ubuntu 13.10. There's a good thread with proper comments about the thing here, which shows several aspects of the thing: http://www.reddit.com/r/PHP/comments/1ksnzw/php_json_removed_in_php_55/ Do not forget the fact, that the reason it was removed was that it had this line together with its license: The Software shall be used for Good, not Evil. which makes it 'non-free' software. Have a look at the entire license here, and see for yourself. http://www.json.org/license.html It's still a possibility to simply ship the php-json included in php, instead of potentially breaking thousands of server setups that rely on a php-json conforming to the json standard. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1287726] Re: Wrong evaluation whether json is valid or not
So the upstream json-c developers don't consider this a bug: Oh, I see. You want json-c to validate that the input being parsed actually is UTF-8. While that might seem reasonable to do at first glance, json-c has historically supported something closer to exact, uninterpreted bytes for strings rather than strict characters, and unconditionally changing this now will be a significant change. Although not strictly to the spec, in many cases I see a value in being able to handle arbitrary data. This is also in conflict to efforts to support even less string-like data as mentioned in Issue#108. Given this, and the fact that performing the additional validation will likely add more overhead to the parsing, any checks to ensure that strings only contain valid UTF-8 sequences would need to be explicitly requested, perhaps by setting the JSON_TOKENER_STRICT flag. Do you happen to have a patch to cause this validation to be done? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287726] Re: Wrong evaluation whether json is valid or not
This also means, that unless the Ubuntu maintainer fixes it either way, then php-json has a rather important change in behaviour between 12.04 LTS and 14.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/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287726] Re: Wrong evaluation whether json is valid or not
Problem is that the old php-json package conforms to the json standard, and the new one does not. If someone went through the effort (we do not have the resources, unfortunately) to make json-c conform to the json standard with said flag, then yes - you could simply compile the package with that flag enabled, and all would be good. The impact of the bug? Json is used all over the place for many years, since it's a very good lightweight format for exchanging data. All of the services provided on a Ubuntu system will potentially break, since it does not conform to the json standard that everyone else does. We had to switch our servers that was running Ubuntu since 2010 to NetBSD to get a modern PHP with proper json handling. Our unit tests broke immediately when we switched to Ubuntu 13.10. There's a good thread with proper comments about the thing here, which shows several aspects of the thing: http://www.reddit.com/r/PHP/comments/1ksnzw/php_json_removed_in_php_55/ Do not forget the fact, that the reason it was removed was that it had this line together with its license: The Software shall be used for Good, not Evil. which makes it 'non-free' software. Have a look at the entire license here, and see for yourself. http://www.json.org/license.html It's still a possibility to simply ship the php-json included in php, instead of potentially breaking thousands of server setups that rely on a php-json conforming to the json standard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287726] [NEW] Wrong evaluation whether json is valid or not
Public bug reported: # php -r 'var_dump(json_decode(\\xff\));' string(1) � Should be: # php -r 'var_dump(json_decode(\\xff\));' NULL Since a large (and growing) number of services use JSON for communication, it's quite bad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: php5-json 1.3.2-2build1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 14:34:43 2014 Ec2AMI: ami-8df705fa Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: c3.xlarge Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: php-json UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php-json (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php-json in Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+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 1287726] [NEW] Wrong evaluation whether json is valid or not
Public bug reported: # php -r 'var_dump(json_decode(\\xff\));' string(1) � Should be: # php -r 'var_dump(json_decode(\\xff\));' NULL Since a large (and growing) number of services use JSON for communication, it's quite bad. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: php5-json 1.3.2-2build1 ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5 Uname: Linux 3.13.0-15-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Mar 4 14:34:43 2014 Ec2AMI: ami-8df705fa Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: c3.xlarge Ec2Kernel: aki-52a34525 Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: php-json UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php-json (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287726 Title: Wrong evaluation whether json is valid or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php-json/+bug/1287726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 574910] Re: High load averages on Lucid while idling
Is this fix present in 2.6.32-312-ec2? I'm seeing high loads on machines doing almost nothing after upgrading to the grub kernel (thanks for that, BTW!), and then -312. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574910 Title: High load averages on Lucid while idling -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
