http://bugzilla.suse.com/show_bug.cgi?id=1128467
http://bugzilla.suse.com/show_bug.cgi?id=1128467#c2
Matthias Gerstner
Since the latest ghostscript update, printing basically any document fails with "filter failed" log message. [...] I believe this was introduced while working on bug 1117336. I'm all for security, but isn't it bit harsh to break printing completely without explicit warning or notice, and without any error messages that might give users a clue where to look?
Thank you for your analysis. This is certainly caused by the recent change in the AppArmor profile. We did of course not intend to break printing. We are working on hardening Ghostscript as far as possible, which is difficult, because it is used extensively in printing but also from various contexts to potentially interpret untrusted data. Sadly, to some extent, Tumbleweed as a rolling release also means that users end up to be testers. Which helps us also, however, in fixing these things and we rely on reports such as this one. I'm assigning this to Johannes who introduced the new profile. He is currently on a trip so fixing it may take a couple of days. -- You are receiving this mail because: You are on the CC list for the bug.