It is not possible to print in evolution as packaged in mageia 8. It is due to a bug in webkit and sandboxed code for printing, see: - https://gitlab.gnome.org/GNOME/evolution/-/issues/1141 - https://bugs.webkit.org/show_bug.cgi?id=202363 How reproducible: Try to print a mail, either on a real printer or in a pdf file. Evolution shows an error message (like: The printer replied “Error opening file â/home/XXXXXX/Documents/testout.pdfâ: No such file or directory”.) and nothing happens (no file created nor printing on a printer). Steps to Reproduce: 1. Launch evolution program. 2. Try to print a mail, either on a printer or in a pdf file. Possible workaround: add "export WEBKIT_FORCE_SANDBOX=0" in the file ~/.bashrc and restart the user session. It will then affect all gtk webkit based applications. Please follow the progress of this bug to solve it when possible.
Thank you for the report, the references, and the workaround. "Until we manage to fix this, you should not enable the sandbox if you need printing to work." They talk of 'WebKitGTK', but I cannot find anything of that name chez Mageia, the nearest being: webkit2 lib64webkit2gtk4.0_37 As for the workaround, it begs the question of where the 'sandbox' is being invoked. Assigning to the Gnome people.
Source RPM: evolution-3.38.3-2.mga8.src.rpm => evolution-3.38.3-2.mga8.src.rpm, webkit2-2.30.5-1.mga8.src.rpmAssignee: bugsquad => gnome
CC: (none) => curtis_mageia
Thanks Vincent. Added: https://wiki.mageia.org/en/Mageia_8_Errata#Printing_in_gtk_webkit_applications
Summary: Can not print in evollution (and other gtk webkit app based) => Can not print in Evolution (and other gtk webkit app), Workaround in c0Keywords: (none) => IN_ERRATA8CC: (none) => fri
We have the errata entry also in Mageia 9 currently. But does it work in Mageia 9 without the workaround and errata 9 entry be removed?
We stopped supporting Mageia 8 almost 8 months ago https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/ That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not. If this particular bug did not get fixed for Mageia 8, then we do regret that. If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field. If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing Mageia is a community project, meaning that we, the users, make Mageia together. The more active contributors we have, the more bug reports will get fixed. Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D
Status: NEW => RESOLVEDResolution: (none) => OLD