From owner-freebsd-chromium@freebsd.org Sun Jan 17 21:00:08 2021 Return-Path: Delivered-To: freebsd-chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 650014D795B for ; Sun, 17 Jan 2021 21:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DJnP41vggz4W58 for ; Sun, 17 Jan 2021 21:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: by mailman.nyi.freebsd.org (Postfix) id 34B504D795A; Sun, 17 Jan 2021 21:00:08 +0000 (UTC) Delivered-To: chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 320014D7959 for ; Sun, 17 Jan 2021 21:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DJnP36y8Lz4Vjt for ; Sun, 17 Jan 2021 21:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D8D4710E for ; Sun, 17 Jan 2021 21:00:07 +0000 (UTC) (envelope-from bugzilla-noreply@FreeBSD.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 10HL0709079738 for ; Sun, 17 Jan 2021 21:00:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Received: (from bugzilla@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10HL072e079737 for chromium@FreeBSD.org; Sun, 17 Jan 2021 21:00:07 GMT (envelope-from bugzilla-noreply@FreeBSD.org) Message-Id: <202101172100.10HL072e079737@kenobi.freebsd.org> X-Authentication-Warning: kenobi.freebsd.org: bugzilla set sender to bugzilla-noreply@FreeBSD.org using -f From: bugzilla-noreply@FreeBSD.org To: chromium@FreeBSD.org Subject: Problem reports for chromium@FreeBSD.org that need special attention Date: Sun, 17 Jan 2021 21:00:07 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.34 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Jan 2021 21:00:08 -0000 To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status | Bug Id | Description ------------+-----------+--------------------------------------------------- New | 247175 | www/chromium: Change location of machine-id Open | 245968 | www/firefox 75.0_2,1 & www/chromium 81.0.4044.113 New | 233095 | www/firefox geolocation no longer working 3 problems total for which you should take action. From owner-freebsd-chromium@freebsd.org Mon Jan 18 10:03:29 2021 Return-Path: Delivered-To: freebsd-chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D7D654E7123 for ; Mon, 18 Jan 2021 10:03:29 +0000 (UTC) (envelope-from freebsd@rheinwolf.de) Received: from mx-smtp.rheinwolf.de (mx-smtp.rheinwolf.de [78.46.88.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4DK6mw6FHHz3jsg; Mon, 18 Jan 2021 10:03:28 +0000 (UTC) (envelope-from freebsd@rheinwolf.de) Date: Mon, 18 Jan 2021 11:03:18 +0100 From: Matthias Wolf Subject: Re: Fwd: [Action Required] Update on Google API usage in Chromium To: =?iso-8859-1?b?UmVu6Q==?= Ladan Cc: chromium-list freebsd Message-Id: <1610964198.73956.0@rheinwolf.de> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed X-Rspamd-Queue-Id: 4DK6mw6FHHz3jsg X-Spamd-Bar: --- X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[rheinwolf.de:s=default]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[78.46.88.170:from:127.0.2.255]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[rheinwolf.de:+]; RCPT_COUNT_TWO(0.00)[2]; DMARC_POLICY_ALLOW(-0.50)[rheinwolf.de,reject]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[78.46.88.170:from]; ASN(0.00)[asn:24940, ipnet:78.46.0.0/15, country:DE]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-chromium] X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 10:03:29 -0000 There seems to be a discussion on the chromium-packagers list for this: https://groups.google.com/a/chromium.org/g/chromium-packagers/c/SG6jnsP4pWM/m/cknNqbEwCgAJ Most likely the sync stuff and auto-login on Google sites will break when removing the API keys and supplying the build flag, so I'd expect a few unhappy users (based on the bug reports we had when sync was broken). From owner-freebsd-chromium@freebsd.org Mon Jan 18 11:22:00 2021 Return-Path: Delivered-To: freebsd-chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1F4834E847C for ; Mon, 18 Jan 2021 11:22:00 +0000 (UTC) (envelope-from rene@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "freefall.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DK8WX0TL2z3ndq; Mon, 18 Jan 2021 11:22:00 +0000 (UTC) (envelope-from rene@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1610968920; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PWhtx1d9A7MRRBTySTvv1Q55pVHAUWgpQY4kKpkCGr8=; b=FewURqyxMSXRSb+/JtKtJpS82zLFMB8+Ty3nf0fc4pp+tjJgrdC95dxGaXQiEiWHJfb3mJ +rbTCArYJ8t44mDEKVBhBEvkBbd7nas6l1BO/aukdwlxfN1IXQbxqqHwZ5ih+lskp/IPWA Kdc3Hd46nk5kgCzIKRmhhQownTsjRLcZINqPsu/W2PQnsInfdPK16v2RMQV8ZWax2sQmuK royunFJ5LopZZdSY7Kx6to58b942xclSb38nreZRUmQk5HsM0lLaoQIfxuu41w0jgxN0vs koAn+wwcOJ4XseM+5S/o7kVf1dGfoT1D5aQOjRfKgmdYcUumxLeoKgTG+b8Qlw== Received: by freefall.freebsd.org (Postfix, from userid 1185) id ED24D193F7; Mon, 18 Jan 2021 11:21:59 +0000 (UTC) Date: Mon, 18 Jan 2021 11:21:59 +0000 From: Rene Ladan To: Matthias Wolf Cc: chromium-list freebsd Subject: Re: Fwd: [Action Required] Update on Google API usage in Chromium Message-ID: <20210118112159.GB43583@freefall.freebsd.org> References: <1610964198.73956.0@rheinwolf.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1610964198.73956.0@rheinwolf.de> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1610968920; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=PWhtx1d9A7MRRBTySTvv1Q55pVHAUWgpQY4kKpkCGr8=; b=oYSVG9tXNTeDonsAYZbLEyAmjKgq2dAMiImvODvr1Snlc/P0Lo2BexTAFuKndfRCum+chQ 3UmWnPdbzJ2w1QXVRhcRf5tCWzzioP8Aq8LJXc9zc5eUmgGRZZ/7q09OLj6aTvCgrbprPZ KrqO8bgzCQ3mlKP1bnmWdgHsr4PB2IkknihbtfYVTImeOoYg6te5KIGrODxR2Jz9YXTvcj oBurO8TtrJUf6WaoevqCmfJrfWrMXBxKplBrEaaVD6c+BZkWl3PjLBhls6UIgvCaiobpPj O00rH6e3+QRreqACxaEUBUs9NVPxIgmHphMjaUfrDTJp87Rwmkfrae7jipFizA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1610968920; a=rsa-sha256; cv=none; b=dKhkSZCfTqrosE8qPTkRGkcmuua8U/3poBBC/g4e48i5dqLiGluqY/qfghpZf4nAEibF6S nlsr6tSKvUbyQiRA9ujb20ulf+a/9xS83VlPlTXcFbYb3Jn4hzF4gNYxiR8b9lpR3hWvyp A8XuEOw28dG/okAHBHZ8VbIY0T0EZKwPJDAxv8wpqzIJ6O830Z9U/ZPp+mS5UudYwwyaFz 1I/c4Kx1AR1SAbP2pXcD6Zo1HRw7zpqKRpvNkQjcwqo+zcyQwqF66MubgWC1q7QFFIQ7oO kr+xp9LiRiC2xYVPWV726nMjgPuEsGiqzmbmLxloP8sTvAnxAKP/TR1qT7xjgg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jan 2021 11:22:00 -0000 On Mon, Jan 18, 2021 at 11:03:18AM +0100, Matthias Wolf wrote: > There seems to be a discussion on the chromium-packagers list for this: > https://groups.google.com/a/chromium.org/g/chromium-packagers/c/SG6jnsP4pWM/m/cknNqbEwCgAJ > > Most likely the sync stuff and auto-login on Google sites will break > when removing the API keys and supplying the build flag, so I'd expect > a few unhappy users (based on the bug reports we had when sync was > broken). > Yes, see also the mail I forwarded (perhaps using my gmail account). I don think there is much we can do about that? René From owner-freebsd-chromium@freebsd.org Fri Jan 22 23:50:58 2021 Return-Path: Delivered-To: freebsd-chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 070394D944C for ; Fri, 22 Jan 2021 23:50:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DMwxs6c6vz4b2H for ; Fri, 22 Jan 2021 23:50:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id E0D764D9788; Fri, 22 Jan 2021 23:50:57 +0000 (UTC) Delivered-To: chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E09A54D944B for ; Fri, 22 Jan 2021 23:50:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DMwxs5wY1z4b6s for ; Fri, 22 Jan 2021 23:50:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id BEA1727292 for ; Fri, 22 Jan 2021 23:50:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 10MNovop039280 for ; Fri, 22 Jan 2021 23:50:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10MNov4l039279 for chromium@FreeBSD.org; Fri, 22 Jan 2021 23:50:57 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 247862] www/chromium: 83.0.4103.116 browsing issue with FreeBSD web site Date: Fri, 22 Jan 2021 23:50:58 +0000 X-Bugzilla-Reason: CC AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: tatsuki_makino@hotmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2021 23:50:58 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D247862 Tatsuki Makino changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tatsuki_makino@hotmail.com --- Comment #4 from Tatsuki Makino --- I think it is necessary to provide information on what window manager you a= re using regarding this issue. I'm using twm :) and all the form components are not working properly. Fixing the focus of the window will fix it. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.= From owner-freebsd-chromium@freebsd.org Sat Jan 23 04:39:28 2021 Return-Path: Delivered-To: freebsd-chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id B22FE4E3C17 for ; Sat, 23 Jan 2021 04:39:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DN3Lm4PnBz4v4H for ; Sat, 23 Jan 2021 04:39:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 974B14E39CD; Sat, 23 Jan 2021 04:39:28 +0000 (UTC) Delivered-To: chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9714C4E3A54 for ; Sat, 23 Jan 2021 04:39:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DN3Lm3hrKz4tfm for ; Sat, 23 Jan 2021 04:39:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 6C7F62F1B for ; Sat, 23 Jan 2021 04:39:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 10N4dSsc086372 for ; Sat, 23 Jan 2021 04:39:28 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10N4dSW1086371 for chromium@FreeBSD.org; Sat, 23 Jan 2021 04:39:28 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 243593] www/chromium not working on headless servers Date: Sat, 23 Jan 2021 04:39:28 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: tatsuki_makino@hotmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jan 2021 04:39:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243593 Tatsuki Makino changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tatsuki_makino@hotmail.com --- Comment #1 from Tatsuki Makino --- (In reply to gpw928 from comment #0) > [ritz.196] $ chrome What happens if you start chromium with the following command? chrome --disable-gpu --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-chromium@freebsd.org Sat Jan 23 10:26:11 2021 Return-Path: Delivered-To: freebsd-chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6A4F74EF7B2 for ; Sat, 23 Jan 2021 10:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4DNC2q2LDGz3njC for ; Sat, 23 Jan 2021 10:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 504624EF74F; Sat, 23 Jan 2021 10:26:11 +0000 (UTC) Delivered-To: chromium@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 501064EF7B0 for ; Sat, 23 Jan 2021 10:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DNC2q1kNlz3p7d for ; Sat, 23 Jan 2021 10:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 2E831763B for ; Sat, 23 Jan 2021 10:26:11 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 10NAQBNF064124 for ; Sat, 23 Jan 2021 10:26:11 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 10NAQB2v064123 for chromium@FreeBSD.org; Sat, 23 Jan 2021 10:26:11 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 243593] www/chromium not working on headless servers Date: Sat, 23 Jan 2021 10:26:11 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: phil.chadwick@claremont.farm X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jan 2021 10:26:11 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243593 --- Comment #2 from gpw928 --- (In reply to Tatsuki Makino from comment #1) I reported this bug almost exactly one year ago. The test system has been upgraded significantly since then: [ritz.223] $ uname -a FreeBSD ritz.oakes.consulting 11.4-RELEASE-p3 FreeBSD 11.4-RELEASE-p3 #0: T= ue Sep 1 08:22:33 UTC 2020=20=20=20=20 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 [ritz.224] $ chrome --version Chromium 87.0.4280.141=20 I can no longer replicate the problem. Thank you for interest. --=20 You are receiving this mail because: You are the assignee for the bug.=