From nobody Sat May 27 09:40:22 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 4QSxbz6nCVz4WnkT for ; Sat, 27 May 2023 09:40:31 +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 4QSxbx6fHQz3lnj for ; Sat, 27 May 2023 09:40:29 +0000 (UTC) (envelope-from mad@madpilot.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=madpilot.net header.s=bjowvop61wgh header.b="c 9wdCPS"; 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 4QSxbs1KkLz6sc8; Sat, 27 May 2023 11:40:25 +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=1685180420; x= 1686994821; bh=JBm99tKXqbSxsF92kVvZduhIy+qXZMKRZfCfDg6jkl8=; b=c 9wdCPSWbLuUEQXFkBlPm1OP8427RNFgkk5/nriV2RQHsopCeAo1dWNdwZVbXEzoF 9ji/4ZxTBIhEUcnY5vD1/V3OHnZRoWH4nhy8aeswTPsKBFKfIabxjiVU4zlPkmhE F+589s36kzJDE5nyhciXlk4cFMWSkOZUG9dyxE4WYu7sjpScdjgx34LQkWSP47Wa c10tgVFgeCSioSXJEolQNbfwO6Q3sDdQvdf98djdePMiBw3fM06NTK2VBZXaDJoV 8u8ndPosynVFyDNEV8e07IWfb1FSiNEJYv9U9u++0w2naoTsWaaRyVJDYxBQQ5yz +T8G6F/Yn9s+rTxuE+oHQ== 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 UNOe3CrYewtZ; Sat, 27 May 2023 11:40:20 +0200 (CEST) Message-ID: <86da3080-431e-9975-b013-f32a7edba1bf@madpilot.net> Date: Sat, 27 May 2023 11:40:22 +0200 Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Content-Language: en-US To: Olivier Duchateau , xfce@freebsd.org References: <89309d8f-6082-615d-34db-3f85138b6e39@madpilot.net> <8cce5d21-dbb7-218b-09ae-df3f81934325@gmail.com> From: Guido Falsi In-Reply-To: <8cce5d21-dbb7-218b-09ae-df3f81934325@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spamd-Result: default: False [-1.93 / 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.93)[-0.928]; DMARC_POLICY_ALLOW(-0.50)[madpilot.net,quarantine]; R_SPF_ALLOW(-0.20)[+mx:c]; R_DKIM_ALLOW(-0.20)[madpilot.net:s=bjowvop61wgh]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[xfce@freebsd.org]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_TO(0.00)[gmail.com,freebsd.org]; MIME_TRACE(0.00)[0:+]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[madpilot.net:+]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; TAGGED_RCPT(0.00)[]; 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: 4QSxbx6fHQz3lnj 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 11:09, Olivier Duchateau wrote: > Le 27/05/2023 à 10:44, Guido Falsi a écrit : >> 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! >> > > Hi, > > On AMD, I have been using xf86-video-vesa, worth to try. It has been working quite fine with drm drivers up to two days ago, before this last update. Anyway it's something I'm going to try, at least as an experiment. I've also been suggested to try forcing X11 to use DRM2. While I do want to have my laptop working, what I really am trying to do is understand what has caused it to break and if it could affect more users. > > In .xsession-errors is there something related to xfwm4? > .xsession-errors contains the error i posted in the xfce bug report: (xfwm4:2083): Gdk-ERROR **: 22:27:41.448: The program 'xfwm4' received an X Window System error. This probably reflects a bug in the program. The error was 'BadAlloc (insufficient resources for operation)'. (Details: serial 1728 error_code 11 request_code 149 (unknown) minor_code 2) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) There's also a backtrace there. -- Guido Falsi