OK thanks. I was not convinced that this bug was not related to both
issues so I thought it better to include both in the same bug report.
Pascal De Vuyst wrote:
> @John Cottier
>
>> The gnome print manager auto detected and intalled the correct driver, but it would not work.
>> The print job would start and then stop on an unknown error.
>> Logging back into KDE was the same.
>>
>
> This looks like a regression in gutenprint 5.0.0.99.1 for your specific printer: Epson Stylus Photo 895. Please open a new bug for this issue to avoid adding unrelated information into this bug report.
> Can you install your printer again in GNOME and attach the output of the printingbug info script and the CUPS error log in the new bug report as described here: https://wiki.ubuntu.com/DebuggingPrintingProblems. This will give us more information about the unknown error you are getting.
>
> Please also attach the output of the printingbug info script with the
> 870 driver installed, so we know the exact driver you are using at this
> moment without problems.
>
>
OK thanks. I was not convinced that this bug was not related to both
issues so I thought it better to include both in the same bug report.
Pascal De Vuyst wrote: /wiki.ubuntu. com/DebuggingPr intingProblems. This will give us more information about the unknown error you are getting.
> @John Cottier
>
>> The gnome print manager auto detected and intalled the correct driver, but it would not work.
>> The print job would start and then stop on an unknown error.
>> Logging back into KDE was the same.
>>
>
> This looks like a regression in gutenprint 5.0.0.99.1 for your specific printer: Epson Stylus Photo 895. Please open a new bug for this issue to avoid adding unrelated information into this bug report.
> Can you install your printer again in GNOME and attach the output of the printingbug info script and the CUPS error log in the new bug report as described here: https:/
>
> Please also attach the output of the printingbug info script with the
> 870 driver installed, so we know the exact driver you are using at this
> moment without problems.
>
>