Good thing I found the fix in the Chromium issues list because I was already tempted to disable SELinux altogether.
We are trying to control what the chrome-sandbox is allowed to do, since it is setuid. The bug that you are seeing is caused by a file/directory being created in the homedir with the wrong label on it. In F15 we did not have policycoreutils-restorecond installed by default, which would have fixed the mislabeled directory. We can add this to a comps file to make sure it gets installed in the future. In F16 we have the ability to label these
files/directoriescorrectly on creation.
The quick fix is to execute the following command:
restorecon -R ~/.config |
The command also solves the problem where the Xmarks Bookmarks Synchronizer and Delicious Bookmarks Extensions keeps on crashing on Chrome on Fedora 15.

THANK YOU
sorry for shouting but thanks so much for the fix!
You’re welcome, grebgrub! Glad to help. =)
Worked like a charm!
This problem was driving me insane (I thought it was a flash issue). Imagine my delight when Google returned this post, with all the right keywords represented in the title!
Thanks Randell.
You’re welcome, Scottthomas! =)
[...] Google chrome config files have wrong selinux labels causing some extensions to repeatedly crash. [Bug 710273]. The fix is to run restorecon -R ~/.config. (Source: Randell’s Blog) [...]
Thanks very much for this fix, Randell! Nice blog. I added your RSS feed to my Google Reader page.
Fantastic! This was rather annoying as iGoogle was causing Chrome to crash for me, not great when its your homepage
Thanks for the fix, worked like a charm.
[...] Resolution: Using information at http://blog.randell.ph/2011/06/11/fix-for-aw-snap-while-loading-twitter-in-fedora-15-with-selinux-en… [...]
Thank you!
Thank you, this was working for me.
Thank you. It works!
This is what I got:
Command not found. Failed to search for file: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
awesome, finally able to get to twitter.com again. thank you!
Wow, so simple?? THANK YOU!!!!!
I thought this was bug in Chrome. Thank you so much!
This post is a life-saver! I think for me Chrome was crashing for any site with offline functionality. Thank you for the fix.
Wow! I was desperately trying to access Google calendar! Thank you for posting this!
Super, thanks much for your advice … Chrome finally working properly.
thank you very much. it helped fixing the iGoogle site too
As far as I am concerned, for the normal desktop user of Fedora, SELinux is of the Devil. All my Fedora frustrations come down to problems with SELinux. I just turn it down from enforcing to permissive at each install. SELinux is nothing more than a full time job generator for the creators and serves no helpful purpose but to frustrate Fedora users.
[...] and Fedora’s SELinux, as explained here. The same problem occurs when you open twitter (see this and [...]
[...] Anyway, I went through all of Google’s recommended procedures for dealing with the “Aw, Snap!” page, to no avail. After trying a number of other suggestions, I had given up and figured I’d just use Firefox for these sites. A few days (weeks?) later, I decided to give it a few more minutes of my time and found a site with a useful answer. [...]