As I mentioned in the comment with the list of repositories I am aware that I have many additional repositories and also many not fully officially certified.
As I have also mentioned, I use my machine as a system for producing multimedia files, audio, video, presentations and documents from OCR scans etc …, especially videos.
Typically I install all the software I need with “1clickinstall” systems and, as you know, these bring with them the addition of repoitories that they eventually need.
As soon as a possible package is installed, every time, I immediately enter the repository management and I lower the priority to all the new repositories acquired, in this way the system should never make automatic upgrades from non-standard and non-certified repositories.
Since I initially left all certified repositories at standard level 99, I initially made mistakes by not correctly identifying “new arrivals”, so some non-standard ones could remain active and cause upgrades and therefore possible damage.
I solved this problem with a trick, that is, as soon as I installed the base system, from the DVD, I lower all the standard repositories to the level of priority 97, in this way I am able to understand very clearly which are the standard and certified ones compared to the “new ones arrivals”
As far as I understand, and obviously I could be wrong, in this way the system will update automatically only and only from the most standard repositories, those with priority raised to 97 and, theoretically, never from any other repository that was not present after the first installation.
Apart from the “few” repositories present after a fresh installation, the only repositories that I manually add and that I raise to level 97 are additional repositories that I find in an OpenSUSE wiki page as recommended additional repositories, and therefore, I guess, certified, and no one else.
Over time I found myself observing that this system I used by managing priorities gave me a more stable machine, preventing “experimental” and malfunctioning updates from arriving in the system, corrupting its functioning.
I don’t know, I’m not sure, but I think it is possible that if I have additional repositories, even with lower priority, and a new program requires, as dependencies, newer, and perhaps experimental libraries, these can, during the installation phase, be brought into the system precisely because you find it in the non-standard repositories present.
Or at least I think it works this way, I’m not sure.
This, I believe, is a weak point of having such repositories active, even if at low priority, and that is that, if required by the installation of some program, some “non-standard” packages or libraries can “dirty” the system.
This is what I think, and I seem to have understood, possibly correct me if something escapes me.
Now to the question of cleaning up repositories and packages from removed repositories.
I could, of course, easily remove all repositories that are not standard and certified.
I did it, some time ago, when installing new particular software when I understood that he would try to use non-standard repositories, during the installation phase I asked him to “NOT” keep the repositories used active after the installation.
This was my previous strategy to not “litter” the system with unwanted automatic updates.
In this case, however, I could not possibly keep these additional installed programs manually updated, and from this situation I studied the system of repository priorities and I replaced this strategy with the one I explained above.
In this way the sources of the additional programs are active but do not automatically “dirty” the system.
Obviously this leads to pay attention, during the installation of a new “strange” program, to what is installed, which does not “seem” suspicious, for example by never activating the “automatic supplier change” in Yast, in this way it is me that I have to check if some “non-standard” library wants to overwrite the standard ones and eventually give up the installation of this package.
It’s not a perfect strategy, some non-standard updates can always escape me, of course.
But I need such additional programs for the multimedia work I do, and we come to the matter of removing the packages you mentioned.
So when you say …
May I suggest that, you reduce your list of repositories to only the bare essentials
…I believe that from the point of view of system updates I am, thanks to the priority strategy, in a relatively clean and standard system.
I think I have a “relatively clean and standard” system, not only because I try to pay attention to what I install and dependencies, but also because typically the programs I install tend to need “particular” libraries only in the multimedia field, not it often happens that they want to change standard system libraries.
Although of course it can happen, and it could be out of my control.
Now, I understand that …
“zypper refresh --force” and “zypper verify”
… would lead, once removed the “unofficial” repositories, to go back to a standard system.
But, I guess, it would also mean breaking all the multimedia dependencies that are necessary for the programs I need and use daily and that reside in the removed repositories, correct?
In this way I would be in a position of not being able to have a functioning machine for the specific purposes in which I use it.
Same goes with …
“zypper update --allow-downgrade”
… which would lead to the same situation.
So also this valuable and valid advice …
Then, check for any orphaned packages and, forcibly reinstall them from the main openSUSE repositories
… would not give valid results because obviously all the “special” multimedia programs that I have installed, and that I need, and that require the repositories eventually removed, would no longer work and would be considered orphaned and could not be “fixed” precisely because in the repositories standards do not exist the necessary requirements to make them work properly.
Now, having said that, if you have understood my situation, I understand that the situation is complex.
It is certainly more difficult to understand what is wrong with a non-standard system.
Unfortunately, however, I do not need a standard system but a system that is suitable for creating multimedia files, from many different sources and with many and different processing possibilities, is my “job”.
For this reason it is complex for me, but it is in general, to understand what is badly functioning.
Keeping in mind, however, as I mentioned previously, that the USB malfunction and weakness was present even when the system was just installed, before the addition of the various additional repositories and various necessary programs, therefore also present in a freshly installed “standard system”.
I doubt that “weird” multimedia programs are going to mess with the libraries, and drivers, device management standards.
I think I have to understand how “the detection of USB devices during connection or power on” works, as well as “the management of these devices during use” and understand if there is any anomaly in those systems, which for some reason has failed to be correctly configured or installed during the new system installation.
I have no idea if it will be possible, if it will be easy, maybe it will not be, but to have a working multimedia machine I think I will have to try.
I thought that I could eventually remove the repositories to have a report, typically I see it in Yast in red, of orphans, and start from there to understand if something standard has been polluted and correct it.
But I should then know “what” to check, so what has to do with the anomaly I find.
One thing that, of course, is not useful for me to do is make my machine unusable by uninstalling everything that is not standard, because it would not be a useful machine for my multimedia activity.
I don’t know if I’ve made myself clear.
I don’t know if at this point it is possible to debug the malfunctions.
I hope so.
And I will try.
One thing I occasionally do if I run into glitches that I don’t know how to fix is an “upgrade” installation, of the same system version, from the original DVD.
I think it causes something very similar to what you ask me to do.
When I start it I let it delete all pre-existing repositories.
So when it’s done I find myself with my “special” programs orphaned or not working.
Typically from that situation I start from scratch and get everything I need to work again.
Maybe by installing everything with more caution and attention, and maybe only one program at a time doing tests between one installation and another.
But even if this system often works, it doesn’t always work, it often doesn’t work if, I believe, the problem could be in the configurations saved in the home partition that are not changed except slightly.
I don’t know, it’s a tough job to do, long and tedious, and that may not solve, but maybe I’ll try.
Otherwise the only alternative would be to understand and debug the system as it is to understand what is not working well and solve that single problem, which is perhaps not easy.
I don’t know, tell me what you think and if you see, from your experience, a system to fix without making the machine unusable?
In the meantime, I still thank you very much for the help and information you have provided me so far.
I await your opinion on this, I’m curious to hear your opinion.