I thought it was some stupid bug in Chrome, but it turn out as just a configuration fix in SELinux.
Refer: Randell’s Blog
The fix is just to run:
$> restorecon -R ~/.config
Advertisement
I thought it was some stupid bug in Chrome, but it turn out as just a configuration fix in SELinux.
Refer: Randell’s Blog
The fix is just to run:
$> restorecon -R ~/.config