[SOLVED] broken libraries after update

dan34 · 2013-11-09 14:17:49

I'm getting this error when trying to start akregator:

error while loading shared libraries: /usr/lib/libkontactinterface.so.4: invalid ELF header

When I run the file command on /usr/lib there are several files that are identified only as "data" including the one producing the above error.

I think this started after pacman upgraded a lot of kde libraries a few days ago. At the end of a pacman run, ldconfig gives errors such as:

ldconfig: /usr/lib/libkpimtextedit.so is not an ELF file - it has the wrong magic bytes at the start.

Any ideas on what went wrong and how to fix it would be most welcome.

Last edited by dan34 (2013-11-09 19:22:16)

Trilby · 2013-11-09 14:39:43

The first google result provided this thread which is in line with my first suspicion: you had a corrupted package download. Have you tried reinstalling it (after purging in from the cache)?

dan34 · 2013-11-09 15:27:59

I tried pacman -Qo on the problem libraries. It reports that no package owns them. Then I tried temporarily moving libkontactinterfaces* out of /usr/lib. Now akregator reports that it can't load the lib because it's not there. However, reinstalling kdepim-akregator doesn't pull in any dependencies.

I then ran pacman -Qo on all the files in /usr/lib (/usr/lib/lib*) and find that there are 105 files not owned by any package.

If libkontactinterfaces* exist on your system could you tell me which package they belong to?

Trilby · 2013-11-09 15:35:31

$ pkgfile libkontactinterface.so.4
extra/kdepimlibs

Also this suggests kdepimlibs might not be the only problem:

$ pkgfile -l kdepimlibs | grep "/usr/lib/lib" | wc -l
99

After you reinstall kdepimlibs, you should recheck the pacman -Qo output, and use pkgfile as needed to indentify packages the files should belong to. Perhaps `pacman -Qk` would be worthwhile too.

dan34 · 2013-11-09 15:51:24

kdepimlibs wants to pull in 5 other packages as dependencies. Then I get a long list of "file exists in filesystem" messages. In this case would it be safe to use the -f option to force it to overwrite?

Trilby · 2013-11-09 16:18:38

Yes, this seems to be one of the few times to use --force, but only for the kdepimlibs installation. It also begs the question, though, of how those files got there. Did you install any KDE related software manually? If not, your package database may have been corrupted, which would leave me wanting to check the health of the disk (fscks first, then smartmontools).

Edit: the incorrect elf type would suggest the former: I suspect some libs were manually installed, but the wrong architecture was used. This might even happen with some "click here to upgrade" crap on some tools if they were running as root.

Last edited by Trilby (2013-11-09 16:20:27)

dan34 · 2013-11-09 19:21:15

No KDE packages were installed manually. I checked the disk and didn't turn up any errors. When reinstalling kdepimlibs pacman pulled in akonadi libical libdmtx qrencode prison as dependencies. I couldn't see anything in the pacman log indicating that they had been removed. Seems that the files for some or all of these were present, but it thought the packages were not inststalled.

I reinstalled kdepimlibs using the --force option and everything seems to be OK now.

Thanks for your help on this.

Arch Linux

#1 2013-11-09 14:17:49

[SOLVED] broken libraries after update

#2 2013-11-09 14:39:43

Re: [SOLVED] broken libraries after update

#3 2013-11-09 15:27:59

Re: [SOLVED] broken libraries after update

#4 2013-11-09 15:35:31

Re: [SOLVED] broken libraries after update

#5 2013-11-09 15:51:24

Re: [SOLVED] broken libraries after update

#6 2013-11-09 16:18:38

Re: [SOLVED] broken libraries after update

#7 2013-11-09 19:21:15

Re: [SOLVED] broken libraries after update

Board footer