Comment 28 for bug 308817
Revision history for this message
| Till Kamppeter (till-kamppeter) wrote | #28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Kristian Erik Hermansen, this bug was initially assigned to CUPS by one of the volunteer triagers because he saw that it is about printing but he was not aware of the internals of the printing workflow and all the packages which are involved (in contrary to scanning with SANE where the SANE package contains the core and all drivers). The triager still did a good thing by assigning the bug to CUPS as this way he raised my attention and I started the investigation.
You have discovered this bug report and as at least the symptoms of your problem are the same as of the initial reporter you have marked the bug "Confirmed".
The hint that Ghostscript could be the culprit I got only after you having kicked in. And today I came to the idea that some of the posters here could suffer bug 299918. I made appropriate comments and not having any hint for CUPS being the culprit and also not having done any upload of CUPS which cured the problem for someone posting here I invalidated the CUPS task. No one really proved that CUPS could have caused the bug.