Bug 1893447
Summary: | evolution print does not work | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Don Swaner <greatauk37> |
Component: | webkit2gtk3 | Assignee: | Michael Catanzaro <mcatanza> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 33 | CC: | caillon+fedoraproject, erack, gnome-sig, lucilanga, markus, mcatanza, mcrha, rhughes, rstrode, sandmann, tpopela |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-02 13:42:56 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Don Swaner
2020-10-31 16:57:55 UTC
Thanks for a bug report. That's a bug on the WebKitGTK side, see: https://bugs.webkit.org/show_bug.cgi?id=202363#c2 Hi, can confirm that the mentioned solution from within the WebKitGTK bugreport that Milan posts here is working. usr@local > WEBKIT_FORCE_SANDBOX=0 evolution Michael, it looks like people are printing mails a lot, would it make sense to disable sandbox by default in Fedoras, until the upstream bug is fixed (which can be who knows when)? Er, I wouldn't do that, because you are rendering untrusted HTML that anyone anywhere in the world can send to you. Fixing printing is on my TODO, but I don't have an ETA for this unfortunately. (In reply to Michael Catanzaro from comment #4) > Er, I wouldn't do that, because you are rendering untrusted HTML that anyone > anywhere in the world can send to you. Right. It can be a problem for Epiphany, but for example in Evolution it's disabled to use the JavaScript markup from the HTML code. I guess the JavaScript is the main problem, even there can be some (minor?) issues in the HTML parser as well. Anyway, I trust you, I'll left the decision up to you. There are just a lot of bugs about printing filled recently, when people begun to use WebKitGTK 2.30.x. Printing under the sandbox has never worked, so it should be broken with all versions since 2.26. |