From nobody Sun May 28 12:44:59 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 4QTdfn5LXrz4XLRP; Sun, 28 May 2023 12:45:21 +0000 (UTC) (envelope-from mad@madpilot.net) Received: from mail.madpilot.net (vogon.madpilot.net [IPv6:2a01:4f8:1c1c:11e5::1]) (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 4QTdfn0dlCz42CZ; Sun, 28 May 2023 12:45:21 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; none Received: from mail (mail [IPv6:fd5c:5351:d272::3]) by mail.madpilot.net (Postfix) with ESMTP id 4QTdfc0nXTz6wCt; Sun, 28 May 2023 14:45:12 +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 :subject:subject:from:from:content-language:references:date:date :message-id:received; s=bjowvop61wgh; t=1685277897; x= 1687092298; bh=v2aG55yGD2DmtVs2gyaBIdmcUJsR42Ljc/xpfRc7PVg=; b=K Tc+1Ff5W3Tl3N8WEQzll8caxSooVEusNTBN5WUfJ6tg1le7jjIH7UoA4q48kShIp bIy9J6MFcdRgv9++MoGCUdc9EWU0+3hG3Ez0xfMKT6rCTTjGCldg45r44znD9UyW aHVO2B9fmBvPqinDolkZiANcvCHgjPEjokAXncgWW0GYGJlPrsG0Zb0YCLygKI2s fiIDaoQ4xm0jQJhpYMVZxnTPUWxV32Y+1bDEh0jNL8qgzjNKg6AH27jN3JwJOB9I 0I52gXU4+g0IffzpKGG+aeQ5IM+mmefRAfRGLAyvic0zK1cRq68CQhlfyf9YXSUl Pc5XL5J/dR3KHEldDdkRg== 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 IVVO3DX7oWOi; Sun, 28 May 2023 14:44:57 +0200 (CEST) Message-ID: <0bc444f5-b078-6874-8655-999dd0e2a68d@madpilot.net> Date: Sun, 28 May 2023 14:44:59 +0200 To: Alastair Hogge , freebsd-current@freebsd.org, current@FreeBSD.org, freebsd-x11@freebsd.org References: <0edab5e7-70db-9b32-39da-54b1503ab824@madpilot.net> <2931778c-9d23-90b8-719f-e34cfa41f188@madpilot.net> <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> Content-Language: en-US From: Guido Falsi Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head In-Reply-To: <226125B8-01E1-44B2-956B-A3CCECF56F7A@riseup.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4QTdfn0dlCz42CZ X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:24940, ipnet:2a01:4f8::/32, country:DE] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated 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 00:42, Alastair Hogge wrote: > Hello, > > Is there some way to test your X session with minimum components, and > slowly adding whatever XFCE does? Maybe I was not perfectly clear. Xorg works fine, I already tested with another window manager. The only thing that changed is that I updated to more recent head, updated a bunch of ports (none directly related to Xorg/DRI3) and xfwm4 started crashing with the errors I reported. Everything else seems to work fine (except other xfce components that depend on xfwm4, which show various degrees of bad behavior caused by xfwm4 not running). xfwm4 was NOT updated or reinstalled. > > I would switch from using a X Display Manager, and launch X from the > login vty using startx (if not already ), with a minimum .xinitrc. I > would find out what is needed to get a minimal XFCE going, for example, > maybe just the Window Manager, no Compositor, or nothing at all to see > if X handles the display mode setting at all. As I said this is something already easily tested. Everything works except xfwm4 crashes on startup if DRI3 is enabled. I am reasonably sure xfwm4 would not crash if compiled without compositor support, since the crash happens in code that is protected by ifdefs and would be removed is disabling compositor. That should would also not run if disabling the compositor, so I'm reasonably sure that would be another possible (but even uglier than disabling DRI3) workaround. > > Also, where are your X logs? It is is normally at /var/log/X.something. > It this log empty after the crash? As stated before I posted a bug report with xfce: https://gitlab.xfce.org/xfce/xfwm4/-/issues/722 Please go there, there is the relevant line from .xsession-errors and a backtrace from the core file xfwm4 left behind. As a further note, for my usage keeping DRI3 is not a problem, so if the only worry I had was to get working xfce on my laptop I would be finished. What, instead, I'd like to try to understand is what is causing this and if it could affect more users in the future. -- Guido Falsi