On Thu, Jun 01, 2023 at 09:02:54AM -0700, Brian Vaughan wrote: > I have good news and bad news. > > The good news is that the issue seems to have been fixed as of today. I > don't get the error popup, and Help > Dependencies shows pylsp_black > installed and at version 1.21. > > The bad news is I'm not sure what fixed it. I realized I made the mistake of > following my daily routine of updating my system, which is not a good idea > when troubleshooting. I checked the changelog dates on the dependencies for > python3-spyder, and the most recently updated were python3-pygments on April > 19, and python3-cookiecutter and python3-sphinx on March 29. > > The only updates today were chromium, chromium-common, and chromium-sandbox, > updated to 114.0.5735.90-2. Maybe those are indirect dependencies?
Oh :( Well, I'm glad it's now working, but as you say, it will be probably now be impossible to identify the source of the bug. I had a quick look at the previous version of the chromium packages, and there's nothing obvious there, so that's almost certainly not the cause. I wonder whether it's a package you updated yesterday that fixed things? You could check the aptitude logs (assuming you used aptitude). Best wishes, Julian
