Your error_log shows only one job (Job 14) which is sent to your auto- generated raw queue (Kyocera-FS-1030D) and completed successfully. This job did not run Ghostscript at all and so it could have never caused a crash of Ghostscript.
The crash must have been caused by your manually generated queue named FS-1030D. If you cannot reproduce the bug any more by printing through your FS- 1030D queue, please tell and we close the bug report. If you can reproduce it, please post the eror_log and the captured print data for a job which has actually caused a Ghostscript crash. In general, you do not need to manually create a print queue pointing to a printer shared by a remote CUPS server. Such queues get generated automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314539 Title: gs crashed with SIGSEGV in TrioWriteDouble() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1314539/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
