A day ago I disabled Chromium extensions via chromium-browser --disable-extensions, as advised in many answers to this problem.
After that I successfully re-enabled them with chromium-browser --enable-extensions, which opens Chromium from the terminal.
However, whenever I start Chromium from Unity Launcher now, it opens with extensions disabled. Could anyone explain to me how I can re-enable them permanently for sessions initiated from the Launcher?
--disable-extensions should only apply to the session you launched with that parameter. It does not change settings. Are you sure you did not do anything else, like delete/rename your session directory as well?
See my post here for a work around and test packages for the original crash issue.
I would find the .desktop file and enable the Exec command to include the desired setting --enable-extensions that way the setting is parsed even when you launch it from unity or gnome.
I figured it out: When dealing with the current Chromium problem mentioned above, I must have accidentally created a file ~/.local/share/applications/chromium-browser.desktop. Whether Chromium was installed or not, Unity would point to that file only. I presume said desktop file must have stored the info to disable extensions. Deleting it solved the issue.