Latest Updates Can't start apps - libjpeg.so.8

[wolfden]

example:
/usr/lib/chromium-browser/chrome: error while loading shared libraries: libjpeg.so.8: cannot open shared object file: No such file or directory

simply run

equo deptest --ask

if it wants to pull openoffice and you don't want it

equo remove x11-themes/sabayon-artwork-ooo && equo deptest

or you can just do

equo install media-libs/libjpeg-turbo

[gallienus]

Was there some sort of glitch? I did an update for five updates. When that was done I got a message about some old programs that need to be removed. I know it's my fault that I didn't read the list. When I said go ahead and remove them just about all the programs were gone from my system. Although it seems only the programs were removed. When I reinstalled google chromium all my book marks were still there.


Also do I need to go back and reinstall everything? like mythtv and mysqul?

[wolfden]

I don't know about your case without more info, the fix of what to do is in the first post. Reinstalling applications won't help.

[gabvil]

Thanks Wolfden !!! I found this problem today (my pc at work is working flawessly with Sabayon, i say this with proud), and just 2 clicks on the forums and the workarround is posted.

Kind regards !!!

[gallienus]

Yes, mine definitely seems to be an entirely different situation. I got it all sorted out, and thanks for responding so quickly.

[gabvil]

Was there some sort of glitch? I did an update for five updates. When that was done I got a message about some old programs that need to be removed. I know it's my fault that I didn't read the list. When I said go ahead and remove them just about all the programs were gone from my system. Although it seems only the programs were removed. When I reinstalled google chromium all my book marks were still there.


Also do I need to go back and reinstall everything? like mythtv and mysqul?

About this i've seen that the pushed updates from 5 days shows the same revision on the packages.
An example:

Vlc 1.1.7 to 1.1.7

This happens on several files from 5 days to this day, not in all files proposed to the update, but a lot of them shows the same issue.

Paranoic? maybe...

PS: i know this is not the related post to ask but gallienus question make me think a little...

[Wildcat]

Hi guys!
I have a similar problem. The chromium cannot work for the last update.
The error massage really similar: /usr/lib64/chromium-browser/chrome: error while loading shared libraries: libv8-3.0.12.18.so: cannot open shared object file: No such file or directory

I did what wolfden have suggested above, but cannot help me. Do you have any idea how can I repair my chromium? I looked for libv8 (equo search libv8) but "found: 0 entries". Google is the same.

[wolfden]

did you try just reinstalling www-client/chromium ?

[Wildcat]

did you try just reinstalling www-client/chromium ?

Yes, of course. Both with equo and emerge reinstall the chromium, but after it does not work.
If I try to update the system or install a program I get similar message:
>> ++ (14/14) >>> app-admin/sulfur-1.0_alpha30
>> ## Unpacking package: app-admin:sulfur-1.0_alpha30~0.tbz2
>> ## Installing package: app-admin/sulfur-1.0_alpha30
>> ## [Sulfur, the Entropy Store (Sabayon Package Manager GUI)]
>> ## Updating database: app-admin/sulfur-1.0_alpha30
>> ## Cleaning previously installed application data.
>> ## SPM: post-remove phase
Traceback (most recent call last):
File "/usr/lib/entropy/libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 2369, in _pkg_foorm
packages_data)
File "/usr/lib/entropy/libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 2129, in _portage_doebuild

File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 563, in doebuild
use_cache, mydbapi)
File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 249, in doebuild_environment
["SRC_URI"], mytree=mytree)
TypeError: aux_get() got an unexpected keyword argument 'mytree'
>> ## QA: Cannot run Source Package Manager trigger for app-admin/sulfur-1.0_alpha28.
>> ## Please report it. Attach this: /var/log/entropy/entropy.log [postrm]
>>> Regenerating /etc/ld.so.cache...
>> ## SPM: post-install phase
Traceback (most recent call last):
File "/usr/lib/entropy/libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 2279, in _pkg_fooinst
)
File "/usr/lib/entropy/libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 2257, in _pkg_setup
def _pkg_config(self, package_metadata):
File "/usr/lib/entropy/libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 2129, in _portage_doebuild

File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 563, in doebuild
use_cache, mydbapi)
File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 249, in doebuild_environment
["SRC_URI"], mytree=mytree)
TypeError: aux_get() got an unexpected keyword argument 'mytree'
>> ## QA: Cannot run Source Package Manager trigger for app-admin/sulfur-1.0_alpha30.
>> ## Please report it. Attach this: /var/log/entropy/entropy.log [postinst]
>> ## Cleaning: app-admin/sulfur-1.0_alpha30
>> @@ Installation complete.
>> @@ Nothing to remove.
>> @@ Configuration files scan complete.
kittus-sabayon kittus #

What should be the problem?

[wolfden]

not enough information and since you seem to be mixing portage with it, augh.

What sabayon are you exactly using, what version of entropy?