On 06/18/13 20:18, Daniel J Walsh wrote: > > > > Suggestion as to how to fix? > > This is a known bug in chrome, Basically the libpeerconnection.log should not > be being created, and the package that is doing this should be using the > standard chrome logging system. > > I believe there is a fix available in chrome for this. Yes, google-chrome-unstable-29.0.1541.2-207000 has the fix....
Attachment:
signature.asc
Description: OpenPGP digital signature
-- selinux mailing list selinux@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/selinux
