(giving 2 examples out of many more) When I startup gvim, I get a bunch of warning messages: --- (gvim:51911): Gtk-WARNING **: 17:05:20.769: Theme parsing error: gtk.css:62:33: The - :insensitive pseudo-class - style property GtkMenu:horizontal-padding - is deprecated and shouldn't be used anymore -- It will be removed in a future version -- Use :disabled instead. x 5 in with variations... --- In a similar vein, I can't start 'node' without it dying: node-default: symbol lookup error: node-default: undefined symbol: FIPS_selftest, version OPENSSL_1_1_0g ---- I say similar vein, since the needed solution is to find some set of libraries which will fix the above, but that **won't disrupt other apps**. The problem comes when some apps are updated but aren't updated with all their libraries or are, but some of the libraries had to be restored to restore other apps to working condition... Especially true on 'node' which I spent some time trying to get working some time back -- damaging other apps (including gvim) that needed different versions of the same libraries. For some things, static linking is likely the safest solution, but for others, supporting multiple library versions that live side-by-side, with apps pulling in the version they need being, likely the best solution for the widest number of apps. I'm quite willing to take suggestions about how to load a version of node that will pull in its needed libs. I'm working around the gvim problem by using a filter around gvim, but that's obviously a hack. One suggestion that needs to happen -- rpms need to stop deleting static versions of libs. One example given of why static linking is broken -- that gnu's glibc uses it to pull in different versions of resolution based on schemes that could be handled in plugins. Bash has developed a similar wart, in that if you disable dynamic, load-time linking it also disables its plugin-support. I'm not sure if this a malicious compliance to disable run-time configuration or some accidental misunderstanding, but haven't investigated that -- just not enough time. I'm not capable of investigating every problem, and am less capable now as I am slower at reading and some compute tasks due to having had a stroke a few months ago, which has left me with holes in my visual field and in my memory. Dealing with the fallout of that and with addon problems caused by questionably competent doctors at Kaiser which may result in increased problems significantly limits what I can do for myself these days. I bring up some of these issues that I know I've been shot-down at getting addressed previously, because they haven't gone away and I really don't have the ability to even maintain what I need, let alone move ahead. So many problems I tried addressing in the past are creating derivative problems (like no long being able to generate a new kernel from vanilla due to needing a new bootloader). Anyway -- if anyone has suggestions on how just to get a working node, and following onto that a not-so-noisy gvim, Suggestions would be appreciated. -linda