additionally, if you want to try Steam Big Picture on your system, you have to do this before:

# setsebool -P selinuxuser_execheap 1

I can confirm that it is working very fine on my Fedora 18 x86_64 system.Actually using nouveau drivers, switching to akmod-nvidia-304 very soon and check differences.akmod-nvidia-310 still not available on rpmfusion.

Now downloading:Amnesia: The Dark DescentSuperbrothers: Sword & SorceryTeam Fortress 2Trine 2(None of this games have been tested yet on my configuration)

It may not be sensible from a package management standpoint (I don't really know what the implications are in terms of how package upgrades will happen or whether the akmod will work properly when the kernel is updated) but I'm using akmod-nvidia-310 from rawhide:

It may not be sensible from a package management standpoint (I don't really know what the implications are in terms of how package upgrades will happen or whether the akmod will work properly when the kernel is updated) but I'm using akmod-nvidia-310 from rawhide:

akmod packages are intended to 'fill in the gap' between when a kernel is released and the relevant module (kmod) is released for that kernel. You shouldn't have any issues with kernel updates due to using an akmod.

That said, rawhide is intended mostly for testing purposes. You should either know what you are doing or be prepared for the consequences of breakage.

@immanetize, yes that's right but I'm not sure if yum will be able to find the akmod package again to reinstall it when the kernel is updated as normally happens.

This isn't twitter - nothing special happens with @handle.

Yum will update the kernel, the akmod will already be installed. You'll have that akmod until a newer package comes in an enabled repo. If there isn't a module built for the kernel you've booted, it is the akmod's job to build that module at runtime. The package is not reinstalled, the module is rebuilt.

Steam developers: This is a clear sign you are doing something wrong. Please read http://danwalsh.livejournal.com/6117.html?thread=23525 for more insight - and use the SELinux mailing list if you can't figure out what's going on here. I will *never* be changing SELinux booleans for a game - and I shouldn't have to.

Steam developers: This is a clear sign you are doing something wrong. Please read http://danwalsh.livejournal.com/6117.html?thread=23525 for more insight - and use the SELinux mailing list if you can't figure out what's going on here. I will *never* be changing SELinux booleans for a game - and I shouldn't have to.

I'd also just like to link in my previous bug report about this issue:

mikeym, you should make a bug report in the limited beta forum and use the correct template (Issue report : etc.). I don't think the devs are reading this part of the forum. I also experience the same bug, but I won't have access to my computer soon, so I cannot report it.