Date: Sun, 28 May 2023 10:22:18 -0600 From: Warner Losh <imp@bsdimp.com> To: Guido Falsi <mad@madpilot.net> Cc: Alastair Hogge <agh@riseup.net>, FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Current <current@freebsd.org> Subject: Re: Help request: strange issue with xfce xfwm4 on AMD hardware, running head Message-ID: <CANCZdfqL46mQ5dhm8WWL%2ByE8DUOwCgVqRdLWA1dBoAMA2mxqtw@mail.gmail.com> In-Reply-To: <a33748eb-3334-8776-46f6-07303afd705d@madpilot.net> 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> <CANCZdfpSnaTpNq2yX2c_qcGTaSsjVWtRyd3V3ZALfCXK57WgkA@mail.gmail.com> <a33748eb-3334-8776-46f6-07303afd705d@madpilot.net>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] 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. 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 <mad@madpilot.net> > > [-- Attachment #2 --] <div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, May 28, 2023, 9:20 AM Guido Falsi <<a href="mailto:mad@madpilot.net">mad@madpilot.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 28/05/23 16:41, Warner Losh wrote:<br> > Sill questions. Did you update only some of your packages? You really <br> > 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 very well.<br> > <br> <br> I'm running FreeBSD head here, using pkgbase. I upgraded a few base <br> packages (I create them with poudriere).<br> <br> I also updated the ports tree and updated other ports using the <br> resulting binaries (also created with poudriere)<br> <br> The pkgs that were updated when xfwm4 stopped working were listed in my <br> first post [1].<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">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...</div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">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...</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> I tested downgrading glib, but nothing changed. Other things updated <br> there look completely unrelated (well except the kernel obviously).<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">Yea, I've rarely had good luck with that path.</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <br> Now that you mention it, I may have forgot to force poudriere to rebuild <br> the drm-kmod port. I'll try that, just in case!<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto">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.</div><div dir="auto"><br></div><div dir="auto">Warner</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> [1] <a href="https://lists.freebsd.org/archives/freebsd-current/2023-May/003734.html" rel="noreferrer noreferrer" target="_blank">https://lists.freebsd.org/archives/freebsd-current/2023-May/003734.html</a><br> <br> -- <br> Guido Falsi <<a href="mailto:mad@madpilot.net" target="_blank" rel="noreferrer">mad@madpilot.net</a>><br> <br> </blockquote></div></div></div>help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfqL46mQ5dhm8WWL%2ByE8DUOwCgVqRdLWA1dBoAMA2mxqtw>
