From nobody Mon May 29 22:18:50 2023 X-Original-To: freebsd-current@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 4QVVLF5f0yz4XGYC for ; Mon, 29 May 2023 22:19:01 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Received: from www121.sakura.ne.jp (www121.sakura.ne.jp [153.125.133.21]) (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 4QVVLD1ywXz3NYj for ; Mon, 29 May 2023 22:18:59 +0000 (UTC) (envelope-from junchoon@dec.sakura.ne.jp) Authentication-Results: mx1.freebsd.org; dkim=none; spf=none (mx1.freebsd.org: domain of junchoon@dec.sakura.ne.jp has no SPF policy when checking 153.125.133.21) smtp.mailfrom=junchoon@dec.sakura.ne.jp; dmarc=none Received: from kalamity.joker.local (123-1-88-210.area1b.commufa.jp [123.1.88.210]) (authenticated bits=0) by www121.sakura.ne.jp (8.16.1/8.16.1/[SAKURA-WEB]/20201212) with ESMTPA id 34TMIpZS082178 for ; Tue, 30 May 2023 07:18:51 +0900 (JST) (envelope-from junchoon@dec.sakura.ne.jp) Date: Tue, 30 May 2023 07:18:50 +0900 From: Tomoaki AOKI To: freebsd-current@freebsd.org Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Message-Id: <20230530071850.c4af5a8607f23712ef73d2f4@dec.sakura.ne.jp> In-Reply-To: <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> <1635751e73bb8c4c600de231c8d43018@riseup.net> <26a8e862-0d51-b3b3-09c1-4a6193bea60b@madpilot.net> <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> Organization: Junchoon corps X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd13.2) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.43 / 15.00]; AUTH_NA(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-1.00)[-0.998]; NEURAL_HAM_LONG(-0.83)[-0.833]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; R_DKIM_NA(0.00)[]; ASN(0.00)[asn:7684, ipnet:153.125.128.0/18, country:JP]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; R_SPF_NA(0.00)[no SPF record]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_TLS_LAST(0.00)[]; HAS_ORG_HEADER(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_NA(0.00)[sakura.ne.jp]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-current@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QVVLD1ywXz3NYj X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N On Mon, 29 May 2023 21:05:42 +0200 Guido Falsi wrote: > On 28/05/23 20:45, Guido Falsi wrote: > > >> It may well be something broke... but I'm just wanting to be double > >> sure it's against a consistent package set. If something broke, then I > >> can't help. > > > > I see, I did not understand what you meant at first. > > > > What I posted was the result of a simple "pkg upgrade", which is what I > > usually do to update the machine, and usually works quite fine. > > > > I have not tested forcing all packages reinstallation ("pkg upgrade -f" > > if I get it correctly). > > > > That is something I was already planning to do. Will report back > > tomorrow for that. > > > > Well forcing reinstallation of all ports (with rebuilt kmod ports) made > the issue disappear. > > SO it looks like it was really nothing. Sorry for the noise and thanks > for the suggestions! > > -- > Guido Falsi IIRC, drm*-kmod port didn't seem to be updated in the first place. OTOH, generic kernel seems to be updated via pkgbase. This could cause problems with incompatibilities. And fixed with forcibly updating all pkgs. poudliere built new pkg, but pkg doesn't thought it's updated , maybe. -- Tomoaki AOKI