Well, just to document the file, I was surprised to learn where this error actually spawned. I fully expected it to be the result of some of the extras That I added in.
But, you know how they say "step-wise refinement" etc?
So I started with a fresh install of Gimp 2.10.22...and first confirmed that the advisory reporting that two different plugins were trying to register the same resource, was not happening. There was no such error reported. There were a couple protests, one about x sane and another that I don't recall...but I've been seeing those comments for so long that I think I've grown numb to them.
So then on the pristine, otherwise unspoiled system, I updated Gimp to 2.10.30-1 +b1
And with no other additions or modifications, the error messages about two different plugins trying register GeglOpvector-fill_c
returned. But, the complaints about x sane and whatever the other one was, were now history.
So, while I admit it's completely unscientific, I'm forced to wonder if the update to the new gimp version at the same time "fixed" the old problems, and in so doing enabled the fixed components to contend for resources that yield my current conflict?
Speculating perhaps that's why this conflict has never caused me any observable problem? (I don't have a scanner)
I was really hoping for a solution easier to isolate, such as "well it only started after I added XYZ plugin", but evidently it's not going to be that obvious.
But, you know how they say "step-wise refinement" etc?
So I started with a fresh install of Gimp 2.10.22...and first confirmed that the advisory reporting that two different plugins were trying to register the same resource, was not happening. There was no such error reported. There were a couple protests, one about x sane and another that I don't recall...but I've been seeing those comments for so long that I think I've grown numb to them.
So then on the pristine, otherwise unspoiled system, I updated Gimp to 2.10.30-1 +b1
And with no other additions or modifications, the error messages about two different plugins trying register GeglOpvector-fill_c
returned. But, the complaints about x sane and whatever the other one was, were now history.
So, while I admit it's completely unscientific, I'm forced to wonder if the update to the new gimp version at the same time "fixed" the old problems, and in so doing enabled the fixed components to contend for resources that yield my current conflict?
Speculating perhaps that's why this conflict has never caused me any observable problem? (I don't have a scanner)
I was really hoping for a solution easier to isolate, such as "well it only started after I added XYZ plugin", but evidently it's not going to be that obvious.