[OpenSmalltalk/opensmalltalk-vm] [Ubuntu] libpulse-simple.so.0: cannot open shared object file: No such file or directory (#538)

 

Today encountered the following error when running Squeak in smalltalkCI on ubuntu-latest (as part of a GitHub workflow):

Extracting virtual machine...
Cog VM Information
/home/runner/.smalltalkCI/_cache/vms/Squeak64-Trunk/sqcogspur64linuxht/lib/squeak/5.0-202003021730/squeak: error while loading shared libraries: libpulse-simple.so.0: cannot open shared object file: No such file or directory

Error with status code 127:
264 squeak::prepare_vm /home/runner/.smalltalkCI/squeak/run.sh

If this error turns out to be permanent, I will try to find out why it did not occur before. Maybe an update in the pulseaudio upstream dependency?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/538", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/538", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>

 

Well, a few builds later it worked again ... Sporadic issue.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

<script type="application/ld+json">[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/538#issuecomment-731834000", "url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/538#issuecomment-731834000", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]</script>