From nobody Mon May 02 22:02:25 2022 X-Original-To: dev-commits-ports-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 581221ACCC6C; Mon, 2 May 2022 22:02:35 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from smtp.burggraben.net (smtp.burggraben.net [88.198.69.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.burggraben.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KscXB5SvXz3Hts; Mon, 2 May 2022 22:02:34 +0000 (UTC) (envelope-from cmt@burggraben.net) Received: from elch.exwg.net (elch.exwg.net [IPv6:2001:470:7120:1:127b:44ff:fe4f:148d]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "elch.exwg.net", Issuer "R3" (not verified)) by smtp.burggraben.net (Postfix) with ESMTPS id 0E71DC01828; Tue, 3 May 2022 00:02:27 +0200 (CEST) Received: by elch.exwg.net (Postfix, from userid 1000) id D7EDA3AB04; Tue, 3 May 2022 00:02:25 +0200 (CEST) Date: Tue, 3 May 2022 00:02:25 +0200 From: Christoph Moench-Tegeder To: Craig Leres Cc: Christoph Moench-Tegeder , ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 980444a82fbd - main - www/firefox: update to 100.0 (rc2) Message-ID: References: <202204291458.23TEwiL4068411@gitrepo.freebsd.org> <58e45f7c-b79f-9f14-4df5-00617fee9ea4@freebsd.org> <05c2a241-5d32-24d9-c223-66aa9ca99b75@freebsd.org> List-Id: Commit messages for all branches of the ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-all@freebsd.org X-BeenThere: dev-commits-ports-all@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <05c2a241-5d32-24d9-c223-66aa9ca99b75@freebsd.org> User-Agent: Mutt/2.2.4 (2022-04-30) X-Rspamd-Queue-Id: 4KscXB5SvXz3Hts X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of cmt@burggraben.net designates 88.198.69.140 as permitted sender) smtp.mailfrom=cmt@burggraben.net X-Spamd-Result: default: False [-3.44 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.99)[-0.992]; FREEFALL_USER(0.00)[cmt]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:88.198.69.140]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[burggraben.net]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_FIVE(0.00)[5]; RCVD_IN_DNSWL_MED(-0.20)[88.198.69.140:from]; NEURAL_HAM_SHORT(-0.94)[-0.945]; MLMMJ_DEST(0.00)[dev-commits-ports-all,dev-commits-ports-main]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:24940, ipnet:88.198.0.0/16, country:DE]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] X-ThisMailContainsUnwantedMimeParts: N ## Craig Leres (leres@freebsd.org): > > Works for me, but your description would match a broken dbus setup. > > Has something changed recently with respect to dbus? My desktop systems > configuration is unchanged in months: "Recently" since 94 or so you'll need an active dbus for the remote commands ("new window via firefox commandline") to work if firefox was compiled with dbis support (that's the default here). > dbus_enable="YES" > hald_enable="YES" hald is long dead. > And /usr/local/etc/dbus-1 appears to be using the sample config. I do > see that I upgrade dbus on April 30th: 1.12.20_5 -> 1.14.0. Do I need to > do something differently now? We're down at 1.12.20,1 again, after people noticed problems with the 1.14 version. > I tried upgrading packages on my work desktop today and going from > firefox 100.0,2 to 100.0_1,2 broke firefox in a new way: Never seen that one. > I have a (spare) desktop at work. I upgraded it to firefox 100.0_1,2 and > thunderbird 91.9.0_2 (along with the other packages). I rebooted and > both firefox and thunderbird dump core after a minute or so. Drats. Firefox is running for hours here. > Exiting due to channel error. That rings a bell: there was something about shared memory back in the day, but it's too late here for googling. Regards, Christoph -- Spare Space