Dale wrote: > > OK. Between the two posts, I did the following. I found out that > libxcb.so.1.1.0 belongs to x11-libs/libxcb so I reemerged it. I also > got lucky when I did a ps aux and caught a kioworker process running > which gave me the path. I couldn't do that the other day which made me > think it was something kernel related. I wish KDE would start commands > with something besides a K since the kernel tends to use that. Anyway, > kioworker belongs to kde-frameworks/kio and I have two versions of that > package. One older 5 version and one newer 6 version. So I also > reemerged kio as well, both versions. In the past when I ran into > segfaults like that, reemerging the package tended to fix it. Maybe it > was a bad compile, mismatch between versions or some other weird > problem. Either way, it tended to fix it. I haven't had that problem > in a while but thought it worth a shot, now that I knew what to look for. > > Let's see if that helps end this. At first, I thought my CPU was trying > to go out. I already had a memory stick go bad. I don't need a bad CPU > as well. O_O > > Thanks to you both. Now we wait. > > Dale > > :-) :-) >
Update. I just checked the logs, including those that were rotated. Since I reemerged those packages, not another segfault error in messages. Actually, there is nothing in there about kioworker at all. It seems that reemerging those packages, not sure which one, fixed the problem. Most likely, some version mismatch. I wonder if revdep-rebuild would have caught that? I didn't think of running that. :/ Thanks to both for the tips. Dale :-) :-)
