Nope, what I did was upgrade unsupported variant/fork of 15.0 release, and reverted back to older unsupported variant of 15.0 release.
There's nothing else there to find, i.e. I'm not affiliated in any other way with either project.

Henrik - once again your response is valid, honest, and understood. Given your input on this matter I'm am marking this as unsolved.

I will say that overall my experience with -current has been quite enjoyable. My problems have been very few and far in between even though it is considered beta. It's remarkable when you think about it. If I continue to have issues I will, for sure, take your advice and move to 15.0 but in the meantime I'm still quite happy with what I have chosen.

I also can't help but notice one thing that is very important to remember. When I have a problem I do a lot of searching on the internet for a resolution. In those searches I can't help but to notice that people running Red Hat have issues with Red Hat that, many times, are not resolved. People running Arch have problems that aren't resolved. People running Mint have issues that aren't resolved. Should those people change distributions because they had a problem?

Do a search yourself for "xinit: giving up" as an example and see for yourself. Many, many, many of those posts never get any kind of resolution. In fact I never saw a cause noted for this at other sites let alone a resolution. It wasn't until the posts from Petri that I got an answer that worked. At least I have a forum to visit that has always given me an answer to my issue that gets me back up and running.

So, even though your opinion makes great sense, for now, I'm staying put.

Thanks for your help and input BTW.

Yes, also a bug report without any suggested patch has a value. However, those kind of bug reports are mostly appreciated when current reaches "beta" status with its first release candidate. At that point there is an intention to release everything in current as the next stable version and any showstopper should be reported. Before that, current is more like an "alpha" version and things are supposed to break when new versions of stuff are tested.

If those are few and no one is willing to do some deeper debugging we can only hope that the problem will be solved in the future by a new version from upstream. However, that would require someone to report the bug upstream.

regards Henrik

I am using Mesa 23.0.0 on Slackware 15.0, on an AMD card successfully. Based on my readings of reports here, the problem seems to be attributed to a Nvidia card possibly with the nouveau driver. This is a good thing to uncover and would be great to report upstream. This is why beta testing is helpful when done the right way.

As far as other distros, I think the idea of newer is always better being promulgated more, leads to alot more people on the bleeding edge, and more breakage. I am going to continue to be a fan of slackware promoting stable release cycles. This is the issue pretty much with all other distros, but also there is the one of other distros heavily customizing through patches which adds to the problem mix. I've used slackware current for years, and I can see PV's process is quite good for rooting out issues before they land on everyone. So I will definitely use stable releases for servers and production machines. -current is really only if you need to look ahead and use brand new hardware that can only run there out of box.

1 members found this post helpful.

Henrik - I have taken your advice to heart and moved to 15.0.

XFCE looks a bit different and I had to recompile some COBOL programs but outside of that everything works, including mesa of course.

Thanks again for your input and your honesty.

2 members found this post helpful.