On 10/12/2014 09:30 AM, Gary Roach wrote:
I finally purged libreoffice from my system and then, using locate, removed every LO file left. I then re-installed libreoffice from wheezy-backport to get the amd64 version. This cleared the problem.On 10/11/2014 06:28 PM, Don Armstrong wrote:Thanks for your help. As suggested, I first ran debsum on kate and libreoffice. All check sums were OK. I then ran the reverse-Depends as suggested above on kate. This cleared the problem. Kate now works fine. The reverse-Depends run on Libreoffice returned - E: Couldn't configure pre-depend dpkg:amd64 for libreoffice-common:amd64, probably a dependency cycle.On Tue, 07 Oct 2014, Gary Roach wrote:After cloning my bad drive to a new one and installing the new drive (see previous messages titled excessive CPU usage) i am left with the following problem: Kate and libreoffice.writer refuse to open and give the errorsI would reinstall libreoffice, kate, and all of their dependencies before going too far into this. It's quite possibly that your bad drive had a bad sector or similar in one or more of these programs... especially since you didn't experience these segfaults before, and no one else has either. Something like: aptitude reinstall '?reverse-Depends(libreoffice)~i'; aptitude reinstall '?reverse-Depends(kate)~i'; will do that for you. If they still occur, enable coredumps, and get a backtrace of the coredump using gdb or similar. [You'll also want to install all of the -dbg packages you can for the libraries referenced in the backtrace.]{{{Sorry about the prior message being cut short. I hit the wrong button.}}}In conclusion, I tried re-running the reverse-Depends on libreoffice-common:amd64 but got the usual - 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded - message when there is nothing to do. Libreoffice still doesn't work. Same error of soffice.bin segfault error4 ld-2.13.soGary R
Thanks for all of the help you gave. Gary R.