From owner-freebsd-chromium@FreeBSD.ORG Sun Nov 17 21:34:43 2013 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E0431C0E for ; Sun, 17 Nov 2013 21:34:43 +0000 (UTC) Received: from mail-ie0-x233.google.com (mail-ie0-x233.google.com [IPv6:2607:f8b0:4001:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B730425E4 for ; Sun, 17 Nov 2013 21:34:43 +0000 (UTC) Received: by mail-ie0-f179.google.com with SMTP id u16so7678367iet.38 for ; Sun, 17 Nov 2013 13:34:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=+P0VOoMzS7N1pB1envrql1nDHnbx9P9zEaG0dXTHlXI=; b=Bvq7UEYtnKLvM7NoCH++jlHknGR7OFtDAB99GBg56uhPzfA+lbNsl1c4EWCZ5xCpHQ ssqpbYWoYfpt+Ru+3ibrV5RBomCad61UDMWOR3haQ1cKasKnZuqU8EVd2UTdKdgFdFYO 9PvOl/MuwKtXZq5jJ0kqgnVzv3m+Z3xk16gVUkbaxuiq+WSoVOQf8Fd4K8rJhWTE5DIv 9j2hIo21LyOhs2th2WynHe7Xs6qS04hfP3X1fGjSz2X/eoD9FWyxmMPb2bdvnD61V4RH /Mnl0MQET3uw/Z8NNa4olaOAXxo4YZgSVtDBOJmSxZZ5w//h+ZN/xbBWxioi9dcvOnVb YPww== MIME-Version: 1.0 X-Received: by 10.50.61.35 with SMTP id m3mr11139688igr.56.1384724083157; Sun, 17 Nov 2013 13:34:43 -0800 (PST) Received: by 10.50.1.241 with HTTP; Sun, 17 Nov 2013 13:34:43 -0800 (PST) Date: Sun, 17 Nov 2013 15:34:43 -0600 Message-ID: Subject: Re: Chromium can no longer find flash player From: Rob Belics To: freebsd-chromium@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.16 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Nov 2013 21:34:43 -0000 The problem was caused by a problem with nspluginwrapper caused by the maintainer. Reinstalling and running nspluginwrapper -v -a -i followed by nspluginwrapper -v -a -u fixed it.