Marc Chamberlin composed on 2017-07-22 20:46 (UTC-0700):
Carlos E. R. wrote:
Marc Chamberlin wrote: ...
Wolfgang said " Maybe some library got corrupted? I would try to reinstall the core ones at least (the ones that are used by kdeinit5):" sudo zypper in -f libQt5Core5 libQt5Gui5 libQt5Widgets5 libQt5X11Extras5 Well, what I suggested in my last post https://lists.opensuse.org/opensuse/2017-07/msg00826.html suggested more or less reinstalling all of KDE (patternS). ;-)
was precisely to reinstall everything in the kde patterns ;-) I wrote https://lists.opensuse.org/opensuse/2017-07/msg00814.html about 4 hours before (after Carlos finally went to bed? Friday morning when, after 6AM?), which explained what Marc should share with the "experts", which he eventually did in the forum. An hour later Wolfgang was able to make that suggestion without asking Marc for any additional information. :-D
Thanks Carlos, and kudos to you as well! I suspect all great minds think alike! ;-) Marc I don't suspect all that much, except when it comes to Carlos and me. Both of us are relentless once we get started in any given help thread. :-| And I really appreciate your help as well Felix, I suspect all the experts were converging on the same solution as we got more data and
On 07/22/2017 10:14 PM, Felix Miata wrote: details... It is really wonderful that all of you are willing to take time to help the rest of us and share your expertise....
I still wonder:
1-what went wrong updating to cause the bad libQt5* package(s) installation. That we'll probably never know, unless there's something hiding in the monster /var/log/zypper.log that Marc might dig out. His zypper.log or zypper.log*.xz could contain libQt lines well into 4 digits, maybe even 5, and not worth trying.
Just for grins, I did a "cat zypper.log | grep libQt" and yep there is a lot of hits! Unfortunately I have a cron job that I run weekly to remove the excess *.xz files in /var/log, so at the moment there is only 1 zypper.log*.xz file... I am more that willing to share these if you think it would be helpful.
2-when exactly the updating occurred that went bad. This mailing list thread started on Tuesday, but Marc started a forum thread about this 15 days earlier.
Yeah, initially when things went bad on me, I first asked and started a thread on https://forums.opensuse.org but hit a lull in getting responses so I decided to start a second thread here on this mail list. Both groups have people that have been very helpful in the past so I tend to "flip a coin" in choosing where to ask a question first.
3-Are Axigen and Fail2Ban still broken? Anything else?
Fail2Ban has started working again also, and I didn't need to do anything special for it once the KDE desktop came back up. So I suspect it's problem was related. Axigen is a bit more disconcerting, what I discovered about it was that all of my configurations for it, in its configuration files had disappeared. These are located under /var/opt/axigen. What the Axigen server did, when it cannot find it's configuration files was to reconstruct them with default values, but that breaks its ability to support all the various domains and users that I had configured it for, and my ability to connect to it from anywhere except from localhost. My solution was to simply restore all of its configuration files from a backup recorded about 2 week prior to this failure. I have no idea why these configuration files were lost and had to be recreated. As for anything else, time will tell.. At the moment it looks good but I have not tested all my other services yet. The ones I use the most (daily) are working. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org