The Chromium portable does not work for me in my Fossa9.5 Puppy. Get a "can't open shared libpulse.so.0 error" although that file is present in /usr/lib/apulse in my distribution. A slightly older version of Chrome portable does run without any issues. Any ideas?
Chromium portable not working in Fossapup64 9.5
Moderators: 666philb, Forum moderators
-
bigpup
- Moderator
- Posts: 6993
- Joined: Tue Jul 14, 2020 11:19 pm
- Location: Earth, South Eastern U.S.
- Has thanked: 911 times
- Been thanked: 1528 times
Re: Chromium portable not working in Fossapup64 9.5
what specific Chromium portable version is this?
The things you do not tell us, are usually the clue to fixing the problem.
When I was a kid, I wanted to be older.
This is not what I expected 
Re: Chromium portable not working in Fossapup64 9.5
The newest. Anyways - it runs with LxPupSc so it does not seem a problem with the browser itself. I'll just use a slightly older version of Chrome which does work on everything I want to use it with.
-
mikeslr
- Posts: 2963
- Joined: Mon Jul 13, 2020 11:08 pm
- Has thanked: 178 times
- Been thanked: 917 times
Re: Chromium portable not working in Fossapup64 9.5
"can't open shared libpulse.so.0 error" from Chromium-portable under Fossapup64.
Pre-2nd cup of coffee, so may be 'off-base'.
File-browse into the ...Chromium-portable/Chromium folder, Right-Click the Chromium binary and select ListDD. Then click ListDD's Missing Tab. That will display a list of all missing libs. Most may actually be present / ...Chromium-portable/lib. ListDD doesn't examine the portable folder, only your operating system. But what the list will show is which version of libpulse.so.0 is missing.
As LxPupSc has that the required version of libpulse.so.0, you may be able to flinch it and drop it into / ...Chromium-portable/lib. If you have either Bookworm64 or F-96, their versions of libpulse.so.0 are more likely work without the need to also obtain a bunch of other libs. Although they may have the same names, Slackware's versions of things aren't always the same as 'debian/Ubuntu''s. Indeed, debian can't always use Ubuntu libs.