If running "chromium-browser --disk-cache-size=0" in Terminal doesn't produce the expected result, then it is more than likely a bug in Chromium itself and not something in the setting up of Chromium. For me, editing /etc/chromium-browser/default works correctly.
In addition, you can see what flags were used to launch Chromium by going to about:version. Also, can you try if specifying a small value (such as 50, for 50 bytes) has any effect? It might be that Chromium still needs a little bit of cache space to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1259933 Title: chromium-browser ignores CHROMIUM_FLAGS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1259933/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
