From owner-freebsd-questions@FreeBSD.ORG Mon Jan 21 18:43:51 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4E738226 for ; Mon, 21 Jan 2013 18:43:51 +0000 (UTC) (envelope-from kurt.buff@gmail.com) Received: from mail-ee0-f51.google.com (mail-ee0-f51.google.com [74.125.83.51]) by mx1.freebsd.org (Postfix) with ESMTP id DADE5768 for ; Mon, 21 Jan 2013 18:43:50 +0000 (UTC) Received: by mail-ee0-f51.google.com with SMTP id d17so2966557eek.10 for ; Mon, 21 Jan 2013 10:43:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=nSvGWHC5b6HGvXzMMFHNtq4ildUV1jjKNsliM44mnRo=; b=uxUdAHy1kw/QkgFnxlxHxOJ2/oQz9qCFz3M/mdHHdy1FsmFxt7ng/uCnhvJ3RpC1Bp MRP9F4DSdm2hDnBciecprshAs0QkuA3mj37wfBjX2+0oaWo36ojQLavaeoHwnHK/Dv85 7rGy4D3YtEy+eB2chsBLzc5qmZfOwCBKv0aeIsUc3l8CYhr6k1A1YjvxqPoS75FCBPPi GptdIEvJDLKfctSvy0nzQebLlwQLrhkcKUPmona5Q7H3iECDei79zOVxPTd3kFcDJ0gX yHb9NWkrTf4mrT+SLCQLJzzD5HVftKS+animooam+sSYzrDWrqk7JT8gP2l1sgNr1YHR bSLA== MIME-Version: 1.0 X-Received: by 10.14.2.196 with SMTP id 44mr62959070eef.25.1358793823652; Mon, 21 Jan 2013 10:43:43 -0800 (PST) Received: by 10.14.124.79 with HTTP; Mon, 21 Jan 2013 10:43:43 -0800 (PST) In-Reply-To: <1358787076.2832.10.camel@precise> References: <1358787076.2832.10.camel@precise> Date: Mon, 21 Jan 2013 10:43:43 -0800 Message-ID: Subject: Re: Error upgrading Chromium From: Kurt Buff To: Ralf Mardorf Content-Type: text/plain; charset=UTF-8 Cc: freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 18:43:51 -0000 On Mon, Jan 21, 2013 at 8:51 AM, Ralf Mardorf wrote: > On Mon, 2013-01-21 at 08:30 -0800, Kurt Buff wrote: >> I worked around this by reconfiguring the port so that it doesn't use >> pulseadio, recompiled, and it finished OK. > > IIUC Google doesn't like to add pulseaudio and/or jackd support to their > software. Because you need to be subscribed to Jack devel mailing list > to read the archive, I copied an Email from another person who also is > subscribed to this list. > > "As a follow up on the original topic the Chromium developers have already > implemented CRAS. > > Their main reason is that they are seeking to minimise energy usage in the > OS and not latency or audio routing issues as described in the webpage. > > Apparently even though Pulseaudio is fine for Palm's/HP's webOS it is not > good enough for ChromeOS. > > I have yet to get to the bottom of how badly they have screwed up JACK > integration but it is highly likely that ChromeBooks will not be able to > integrate into a netjack system. > > So, I guess we can expect a new round of pissed off audio users > complaining about the lack of JACK integration with ChromeOS in the coming > years. > > Probably the easiest answer will be for them to stick within their Chrome > eco system in much the same way that Android users have to now." > - http://lists.jackaudio.org/private.cgi/jack-devel-jackaudio.org/2013-January/010592.html Good to know! Since ATM I'm only using Chromium on a netbook (Asus Aspire One - about 3 years old), and it doesn't have much of an audio system, I'm not too worked up about it, but I've got a new Dell laptop coming, and I suppose I'll just have to use one of the other web browsers for that. Thanks, Kurt