From nobody Sat May 27 18:01:37 2023 X-Original-To: xfce@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 4QT8kR5W4nz4V6L4 for ; Sat, 27 May 2023 18:01:51 +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 4QT8kQ3fLjz41hH for ; Sat, 27 May 2023 18:01:50 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=madpilot.net header.s=bjowvop61wgh header.b="s OaAIaI"; 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 4QT8kH07DDz6yqv for ; Sat, 27 May 2023 20:01:43 +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 :from:from:references:content-language:subject:subject:date:date :message-id:received; s=bjowvop61wgh; t=1685210496; x= 1687024897; bh=IgFH6URKHnfRjPGPv+ycz7z2oPz1j1opolHsTztyJuo=; b=s OaAIaI1H6NDYceq42m2LKBlEK78LcTzw00SgafyukMqkLcr8RRTmgunresEOI8Rq Zz4U/oum61PvWIzaDqhHuoLY1uHVON4uAXg1PpQ05Q3RywsXc3B9/GUDgz9IXBIu G/gU/RBsppuA669FQQ7aBtPimhMWETYGd54JLQnccd5zHnvivi2qmdVisCo/HPMa gdwLdrKZ9hGz0TNWJjEXoT+P38g7WZBu7ybrPAq++6g7Qx5/FdI0XOpbvM/5y4hc QSwB+SOcIEgBCN6w0mvWD5gUSqr0kBkQBYMeuQdhaq8t7zMLRCcS/3CGgFyAj/kp 94Qz8qgDL3lX11+46M49g== 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 u6HLQRnm66Ji for ; Sat, 27 May 2023 20:01:36 +0200 (CEST) Message-ID: <09af0b46-2b0b-dcdc-0ac9-2e4ba35e2c90@madpilot.net> Date: Sat, 27 May 2023 20:01:37 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: xfce@freebsd.org References: <89309d8f-6082-615d-34db-3f85138b6e39@madpilot.net> From: Guido Falsi In-Reply-To: <89309d8f-6082-615d-34db-3f85138b6e39@madpilot.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spamd-Result: default: False [-2.00 / 15.00]; MISSING_MIME_VERSION(2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.995]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; R_SPF_ALLOW(-0.20)[+mx]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[xfce@freebsd.org]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; RCVD_COUNT_THREE(0.00)[3]; ASN(0.00)[asn:24940, ipnet:159.69.0.0/16, country:DE]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; BLOCKLISTDE_FAIL(0.00)[159.69.1.99:server fail]; PREVIOUSLY_DELIVERED(0.00)[xfce@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; TO_DN_NONE(0.00)[]; MID_RHS_MATCH_FROM(0.00)[] X-Rspamd-Queue-Id: 4QT8kQ3fLjz41hH X-Spamd-Bar: - X-ThisMailContainsUnwantedMimeParts: N List-Id: XFCE List-Archive: https://lists.freebsd.org/archives/freebsd-xfce List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xfce@freebsd.org X-BeenThere: freebsd-xfce@freebsd.org On 27/05/23 10:44, Guido Falsi wrote: > Forgot to CC this list, here is a link to the message: > > https://lists.freebsd.org/archives/freebsd-x11/2023-May/003306.html > > Short story is, XFCE xfwm4 started crashing on login on my laptop for no > apparent reason, working fine elsewhere, and I have no clue what broke it. > > Could be a local machine issue, but could also something bigger that > will trickle down to more users. Looks related to the graphics hardware. > > Here is also a direct link to the upstream bug I filed: > > https://gitlab.xfce.org/xfce/xfwm4/-/issues/722 > > If anyone has suggestions they are appreciated! > I just tested, as suggested by a friend, disabling DRI3 and now everything works; while it is not a fix is a good workaround. I report here for the record. Now I need to understand what happened that causes it to break, if it's something in our kernel or the drm kmod, or indeed something wrong in xfwm4, I honestly have no clue right now. Disabling DRI 3 is easily accomplished by creating a file in /usr/local/etc/X11/xorg.conf.d with content: Section "OutputClass" Identifier "AMD" MatchDriver "amdgpu" Driver "amdgpu" Option "DRI" "2" EndSection -- Guido Falsi