From nobody Sun May 28 16:22:18 2023 X-Original-To: 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 4QTkTM4jyVz4XZQr for ; Sun, 28 May 2023 16:22:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-ej1-x631.google.com (mail-ej1-x631.google.com [IPv6:2a00:1450:4864:20::631]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QTkTM2Y24z3Kg7 for ; Sun, 28 May 2023 16:22:31 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-ej1-x631.google.com with SMTP id a640c23a62f3a-97000a039b2so464247366b.2 for ; Sun, 28 May 2023 09:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20221208.gappssmtp.com; s=20221208; t=1685290949; x=1687882949; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=xiaMyFYUStuVjS+z4FaK1uAI3uTIKibsEiXvbqe27Hw=; b=IbPDu8gr4sGmKrM5UxkVVYnrGamwJP3z2mP9kpFmbuguBwjoHS36zDbieOSt/UNh+F gz+rWnXaQiZ7ZNLidflFeo2JSZXsW5elV6Epd/I4KS0pNdvInhkt5JjRuN6CHHxTIyLd lEO+uW/ZemaH0f6PL98z9JdXf0XghE7DIK2I3H5xmuBMJngabpsYUOohf1VZZ4cnvJKa J4k5jdX5dmDOiJ5l3IFNYBc+e0JSWTaF++zbAgxdjnwnbK2RKH/aGLdOfzjHtZ8ZCXRZ QYCeb623HOP60zV2cY47fY5AESVoWbwVAcm62KETzO1C2pYvZLVlGqWyznu0Y/uuQZZ/ Htiw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685290949; x=1687882949; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=xiaMyFYUStuVjS+z4FaK1uAI3uTIKibsEiXvbqe27Hw=; b=SgQZU23U3osB/rAa3XSSJmQafUNevRtdWWkhqTv5Q4zCNgUuq49j8Zm0mXSrCoi+ml fLRHoAMSk6VqUV7KnvP1NizkliMafYf5o1rrvFJfN8dAm0zIBFTKNNosYAxQsX42A0Do jsBOB3iuiKwcCIE/b2VV7XCVOm+jLJqY18xqg4sH0IFSx34CEkA/Dtk88ngj5+LLCqho O0GVNZgg24erJ63ySB2d//F5/N7X/AVD0784uKra6enIePeFz+vA14F4+H30MaKS5V0V yzpLy8LwQvdhE+LC2NRBJNmDMZnQc+ZEIyu8dx1EIfqxqH43qnbXnKzkhPzd7yBjAo9R 5qpg== X-Gm-Message-State: AC+VfDxqNtvRzjEw61cw61cs+ZFQtAbDGBCPw8/k2L4HeWzTIdH+XUcr vRICpVbyGRLiIki2HM0gWO5z+8ffRdyXgWFSpdIV4Hl95NIkMsLB X-Google-Smtp-Source: ACHHUZ7+P1PEHq62q5Ciivw6IGgtoXlPh+BZV+Y5qSBACnHtxJc0IaqMuDyRJAcXLAbvUylY6VhmJubf4Pg7OEKJPM8= X-Received: by 2002:a17:907:98e:b0:957:943e:7416 with SMTP id bf14-20020a170907098e00b00957943e7416mr8872669ejc.15.1685290949342; Sun, 28 May 2023 09:22:29 -0700 (PDT) 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 MIME-Version: 1.0 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> In-Reply-To: From: Warner Losh Date: Sun, 28 May 2023 10:22:18 -0600 Message-ID: Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head To: Guido Falsi Cc: Alastair Hogge , FreeBSD Current , FreeBSD Current Content-Type: multipart/alternative; boundary="000000000000610d9305fcc3608b" X-Rspamd-Queue-Id: 4QTkTM2Y24z3Kg7 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-ThisMailContainsUnwantedMimeParts: N --000000000000610d9305fcc3608b Content-Type: text/plain; charset="UTF-8" On Sun, May 28, 2023, 9:20 AM Guido Falsi wrote: > On 28/05/23 16:41, Warner Losh wrote: > > Sill questions. Did you update only some of your packages? You really > > need to update them all at the same time to have them be compatible. > > Some projects have a fast moving abi they don't keep compatible very > well. > > > > I'm running FreeBSD head here, using pkgbase. I upgraded a few base > packages (I create them with poudriere). > > I also updated the ports tree and updated other ports using the > resulting binaries (also created with poudriere) > > The pkgs that were updated when xfwm4 stopped working were listed in my > first post [1]. > So not all of the non pkg base packages? Have you tried updating them all? Or you did update them all and the list of what updated was in the post? I read it when first posted and again now and am unsure which it is... 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. Also a good time to plug zfs root and snapshots to roll back to if the upgrade fails. But that's like for future you... I tested downgrading glib, but nothing changed. Other things updated > there look completely unrelated (well except the kernel obviously). > Yea, I've rarely had good luck with that path. > Now that you mention it, I may have forgot to force poudriere to rebuild > the drm-kmod port. I'll try that, just in case! > That's unlikely the cause. Though it wouldn't hurt. Usually it simply won't load. And this package us matched to a specific kernel so make sure you rebuild against the headers of the kernel installed. Warner [1] https://lists.freebsd.org/archives/freebsd-current/2023-May/003734.html > > -- > Guido Falsi > > --000000000000610d9305fcc3608b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Sun, May 28, 2023, 9:20 AM Guido Falsi <mad@madpilot.net> wrote:
On 28/05/23 16:41, Warner Losh wrote:
> Sill questions.=C2=A0 Did you update only some of your packages? You r= eally
> need to update them all at the same time to have them be compatible. <= br> > Some projects have a fast moving abi they don't keep compatible ve= ry well.
>

I'm running FreeBSD head here, using pkgbase. I upgraded a few base packages (I create them with poudriere).

I also updated the ports tree and updated other ports using the
resulting binaries (also created with poudriere)

The pkgs that were updated when xfwm4 stopped working were listed in my first post [1].

So not all of the non pkg base packages? Have you tried upda= ting them all? Or you did update them all and the list of what updated was = in the post? I read it when first posted and again now and am unsure which = it is...

It may well be = something broke... but I'm just wanting to be double sure it's agai= nst a consistent package set. If something broke, then I can't help.

Also a good time to plug z= fs root and snapshots to roll back to if the upgrade fails. But that's = like for future you...

<= div class=3D"gmail_quote">
I tested downgrading glib, but nothing changed. Other things updated
there look completely unrelated (well except the kernel obviously).


Yea, I've rarely had good luck with that path.

<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">
Now that you mention it, I may have forgot to force poudriere to rebuild the drm-kmod port. I'll try that, just in case!
<= /div>

That's unlikely the = cause. Though it wouldn't hurt. Usually it simply won't load. And t= his package us matched to a specific kernel so make sure you rebuild agains= t the headers of the kernel installed.

Warner

--000000000000610d9305fcc3608b--