Mark Knecht wrote: > On Fri, May 16, 2025 at 3:33 PM Dale <[email protected]> wrote: >> Howdy, >> >> I was looking at messages and ran up on this error. This is on my new >> rig, Gentoo-1. >> >> >> >> May 16 17:20:16 Gentoo-1 kernel: kioworker[3084]: segfault at 0 ip >> 00007f95f17510e8 sp 00007ffe1b492d50 error 4 in >> libxcb.so.1.1.0[7f95f174f000+15000] likely on CPU 15 (core 7, socket 0) >> May 16 17:20:16 Gentoo-1 kernel: Code: e8 2d e9 ff ff 66 66 2e 0f 1f 84 >> 00 00 00 00 00 66 90 f3 0f 1e fa 41 57 41 56 41 55 45 89 c6 41 54 55 53 >> 48 83 ec 48 48 8b 19 <8b> 07 89 74 24 18 48 89 4c 24 08 64 48 8b 2c 25 >> 28 00 00 00 48 89 >> May 16 17:20:17 Gentoo-1 kernel: kioworker[3094]: segfault at 0 ip >> 00007f792db5b0e8 sp 00007ffe35189c40 error 4 in >> libxcb.so.1.1.0[7f792db59000+15000] likely on CPU 12 (core 4, socket 0) >> May 16 17:20:17 Gentoo-1 kernel: Code: e8 2d e9 ff ff 66 66 2e 0f 1f 84 >> 00 00 00 00 00 66 90 f3 0f 1e fa 41 57 41 56 41 55 45 89 c6 41 54 55 53 >> 48 83 ec 48 48 8b 19 <8b> 07 89 74 24 18 48 89 4c 24 08 64 48 8b 2c 25 >> 28 00 00 00 48 89 > <SNIP> > > All of the errors seem to involve libxcb which is part of the graphics > subsystem. If you're not "seeing" any problems then personally I wouldn't > worry too much about it. > > Gemini responds to the query with the following: > > Yes, the error "error 4 in libxcb.so.1.1.0" is a known issue that has > appeared in various contexts, often related to graphical applications > and libraries on Linux systems. > > Based on the search results, here's a summary of what this error can indicate: > > General Protection Fault: This error often arises as a "general > protection fault" or "segmentation fault," indicating that a program > tried to access memory it shouldn't have. The libxcb.so.1.1.0 library, > which handles communication with the X Window System, is often > implicated in these crashes. > > Version Mismatches: In some cases, the error can be due to a version > conflict between different libraries, such as the operating system's > libxcb and a version bundled with a specific application (like > VMware). > > Missing Dependencies: The error can also occur if an application is > missing a related library or plugin, such as a Qt platform plugin that > relies on libxcb. > > Bugs in Specific Software: Sometimes, the error is triggered by a bug > within a particular application (like a game running through Steam or > the Signal Desktop client) that interacts with the X server via > libxcb. > >
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 :-) :-)
