From nobody Mon May 29 19:05:42 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 4QVQ3P3v5Nz4Wl79 for ; Mon, 29 May 2023 19:05:53 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [159.69.1.99]) (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 4QVQ3N4QYQz4DDg for ; Mon, 29 May 2023 19:05:52 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=madpilot.net header.s=bjowvop61wgh header.b="B xN+Gci"; spf=pass (mx1.freebsd.org: domain of mad@madpilot.net designates 159.69.1.99 as permitted sender) smtp.mailfrom=mad@madpilot.net; dmarc=pass (policy=quarantine) header.from=madpilot.net Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QVQ3D5hSWz6jlk; Mon, 29 May 2023 21:05:44 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=madpilot.net; h= content-transfer-encoding:content-type:content-type:in-reply-to :references:from:from:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685387143; x= 1687201544; bh=4KDUeSyq3ltSEZRqKETd5Y2t02jG3w0wg5PyFA3yUyc=; b=B xN+GcivLulb4yho/8JYxnzZmGukwTPxA5+8X6/nEY6tVXy2YhOuw+b6+dKF9uh5y fuN9Njx5lEkoQtsbqf1o3JWTQ3WJRbmu1lkZKA69S2MNeZTejI+hOv6JjGMxlchR iFv7vxewGH7V8gUO5e6bt2jtnBav0IkO0sLjxMLS1oIwKCETvoDKLzuGfCwFPb9t 8joDLqYoJ+oFwJRsTpMYskwhX4qAoctZf4Pdze6YflhsS/wfXg3EjwqV1dcKP4JA TTx7YnmYxaPhkQdwGbUKvo26z1kTYDcQChc5hu9YyVwYovWMQwmVJHgfQIEltMyZ y2ohaQ0WH5jBqqq/Zlecg== Received: from mail.madpilot.net ([IPv6:fd5c:5351:d272::3]) by mail (mail.madpilot.net [IPv6:fd5c:5351:d272::3]) (amavisd-new, port 10026) with ESMTP id AEeolcVPjgct; Mon, 29 May 2023 21:05:43 +0200 (CEST) Message-ID: <7f4e8f75-5a23-d82a-f777-ea2cbbf95cae@madpilot.net> Date: Mon, 29 May 2023 21:05:42 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US From: Guido Falsi To: Warner Losh Cc: Alastair Hogge , FreeBSD Current 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> In-Reply-To: <0d4e3bda-4ef3-2b22-0a95-319f7f9baf23@madpilot.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-1.99 / 15.00]; MISSING_MIME_VERSION(2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.993]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; RCPT_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; RCVD_COUNT_THREE(0.00)[3]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QVQ3N4QYQz4DDg X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N 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 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