Thanks, Vincent. Reading the write-up on that but in the debian link, the behavior I described makes sense. Computer was on Karmic 9.10, the FAH client 6.29 was compiled correctly for the Karmic libraries, so it ran with no issues. I interrupted it to make the upgrade to Lucid 10.04, at that point the FAH client was happily processing an existing work unit. So when I restarted it after the upgrade, it had no need to contact any of the FAH servers until it was finished. When finished, it tried and failed to connect to the FAH server to send the results. But the FAH client's error-trapping must not be very smart, because any connection failure simply puts it in a wait-and-try-again loop. If I hadn't restarted the machine, I never would have know. When I restarted, it gave the "relocation" error, because THEN it tried to connect first, to send results and get a new work unit.
Applied Charlie's workaround, that's working fine now. Gabe, with Vincent's explanation, it makes sense that the problem is on the FAH client and not with any Lucid libraries. Can you close this bug or mark it as resolved, or do I need to do it because I opened it? I have no objection at this point, let's just keep it accessible for the benefit of anyone having the same issue. Thanks. -- Lucid official release 10.04/64-bit Desktop: 64-bit fold...@home client 2.69 crashes in terminal with:relocation error: /lib/libnss_files.so.2: symbol __rawmemchr, version GLIBC_2.2.5 not defined in file libc.so.6 with link time reference https://bugs.launchpad.net/bugs/574726 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
