From nobody Sat May 27 18:03:51 2023 X-Original-To: freebsd-x11@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 4QT8nP75jlz4V6d2; Sat, 27 May 2023 18:04:25 +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 4QT8nP2M67z420s; Sat, 27 May 2023 18:04:25 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=madpilot.net header.s=bjowvop61wgh header.b="D 3jdsam"; 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 4QT8mp1Nj7z6yqv; Sat, 27 May 2023 20:03:54 +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=1685210629; x= 1687025030; bh=+vK2BRnXwEav3ch6EBTpo/q7u+USrrqmSRK4a3c7L/k=; b=D 3jdsamiMB0wGtLpGEozvcHJKtLv0iqeYDwdVnXDFovUMFC2Lx4EcR8qwgAWQLI4+ ugKmHxlzW7VCrxTURlkMNVvq5NjjCTxL5WUFbugT5DQFEqDVcn3DMl4uP1/Akoef 6soXc9eEipz0E+orIlRv8ChIHUoO53kZsbMp8xHpf8KaX32DA0lerRBOUQ2S4lHl LjtdQJbGtauz6o/FUAn91CEIWm+7Nh7oM4UOpnEBHS725uxnHYMLpVHH0Ft6135F hzJDS4NUrqxjb3zuJyr2bXwIJSJ8eGvSsf/JdCNC3xXBzrxfmOp4OFIbJYtLiSBy a+LuQbhMSxnggwe4yXzLQ== 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 AquHq5k-_qj0; Sat, 27 May 2023 20:03:49 +0200 (CEST) Message-ID: <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> Date: Sat, 27 May 2023 20:03:51 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US From: Guido Falsi To: current@FreeBSD.org, freebsd-x11@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> In-Reply-To: <0edab5e7-70db-9b32-39da-54b1503ab824@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_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.988]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; R_SPF_ALLOW(-0.20)[+mx:c]; MIME_GOOD(-0.10)[text/plain]; BLOCKLISTDE_FAIL(0.00)[159.69.1.99:server fail]; MLMMJ_DEST(0.00)[current@FreeBSD.org,freebsd-x11@freebsd.org]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[madpilot.net:+]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TO_DN_NONE(0.00)[]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QT8nP2M67z420s X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org On 27/05/23 10:31, Guido Falsi wrote: > Hi, > > I'm seeing a strange issue with xfwm4 on my laptop running head (commit > 5804b7ab378d6207130bd1685c931da6a4e76e55), using pkgbase, everything > build on poudriere. > > I have filed an issue upstream with a description and some finding: > > https://gitlab.xfce.org/xfce/xfwm4/-/issues/722 > > I'm testing changing some things but I get the same exact error 100% > repeatable. > A friend of mine suggested trying to disable DRI 3 and this indeed allowed xfwm4 to not crash. This is a workaround, not a fix, and does not explain what is causing the behavior. Not sure where I should be looking, I'll also check changes in kernel that could be related. Again if anyone has some insight please share! -- Guido Falsi