Ah! I wasn't aware of the problem if you tried this with evolution still running, good catch! ![]()
If you want to override the default settings so that WEBKIT_FORCE_SANDBOX=0 is set every time, you can try the following:
-
Shut down all instances of evolution
-
Copy the default desktop file to your profile
cp /usr/share/applications/org.gnome.Evolution.desktop ~/.local/share/applications/ -
If you grep the file, you will see there are a number of instances of exec:
grep -i "exec" ~/.local/share/applications/org.gnome.Evolution.desktopExec=evolution %U
Exec=evolution -c current
Exec=evolution mailto:
Exec=evolution -c contacts
Exec=evolution -c calendar
Exec=evolution -c mail
Exec=evolution -c memos
Exec=evolution -c tasks -
Use sed to adjust the exec command to include WEBKIT_FORCE_SANDBOX=0:
sed -i 's/Exec=evolution/Exec=env WEBKIT_FORCE_SANDBOX=0 evolution/g' ~/.local/share/applications/org.gnome.Evolution.desktop -
Grep again to check the updates have taken:
grep -i "exec" ~/.local/share/applications/org.gnome.Evolution.desktopExec=env WEBKIT_FORCE_SANDBOX=0 evolution %U
Exec=env WEBKIT_FORCE_SANDBOX=0 evolution -c current
Exec=env WEBKIT_FORCE_SANDBOX=0 evolution mailto:
Exec=env WEBKIT_FORCE_SANDBOX=0 evolution -c contacts
Exec=env WEBKIT_FORCE_SANDBOX=0 evolution -c calendar
Exec=env WEBKIT_FORCE_SANDBOX=0 evolution -c mail
Exec=env WEBKIT_FORCE_SANDBOX=0 evolution -c memos
Exec=env WEBKIT_FORCE_SANDBOX=0 evolution -c tasks
When you run evolution it may ask to set itself as default, presumably because the system can tell the difference between the command with and without "env WEBKIT_FORCE_SANDBOX=0" added.
I opted to set the new default, but you can just ignore the message if you prefer.
Bear in mind I'm running Fedora, so your paths may or may not be different.
Thanks,
Rob