Hello all,
I am using 32 bit Parrot OS, which is a Debian based security distro. After installing libreoffice from their repos after my initial setup, I couldn’t get any file to open, or any base program to open at all. The splash screen and loading bar would appear and then disappear.
I ran libreoffice --writer from a terminal to get some error output and it showed that “kernel library file /usr/share/pocl/kernel-i686-pc-linux-gnu.bc doesn’t exist.”
The only kernel version I show in my pocl folder is kernel-x86_64-pc-linux-gnu.bc. Strange in itself on a 32 bit system…
I’ve seen other errors with pocl around the web, but no one replies with help. Does anyone have any experience or thoughts about this? Why I would have a 64 bit kernel in the pocl files seems strange to me. Maybe it’s an issue with Parrot OS and they included the wrong one in the 32 bit iso. Probably easy to miss. This is a fresh OS install and I haven’t downloaded anything else yet. I usually do my software installs in the same order and this was first.
I’ll do some searching into pocl to see about getting the 32 bit kernel downloaded and in the right place on it’s own in the meantime to see if that’s the fix.
I may be fixing my own issue while thinking and writing this out, but I want to document in case others need the same solution.
Thanks!
Update: I found this.
It appears there is an incorrect file in the repos for the portable computing language. No idea how to change it though and get the correct one. The file being asked for is 32 bit, but the one being included is 64! I guess I’ll try to ask Parrot OS or a Debian forum.
Update 2: I was asking around the Parrot OS forums and the devs seemed to think I was an idiot because theirs all work. Their answer was to not run it from the terminal and to use the menu option. Clearly they didn’t read that I only ran it from the terminal to see any errors BECAUSE the menu didn’t work. I downloaded a fresh iso of their 32 bit OS. On the live media, the pocl folder has the 64 bit kernel instead of the 32 bit. This seems to be a debian repo issue. I’m going to try a few more tricks and update this accordingly.