Libqt5gui.so.5 Version Qt_5_private_api 39; Not Found
Marziabo Frechette
I tried different solutions from other threads but can't make it. Can anyone help or explain what exactly the problem is? A few days ago I was able to run qtcreator, but when I tried today I got this error. I think it may correspond to the installation of some application, unfortunately I can't say which one, I had to install a few.
Edit: Okay I took some time and tried the solution from here again: Error on execution -version `Qt_5' not found required byand this partially solves the problem. With LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/ qtcreator I can start qtcreator again. But this of course doesn't solve the problem at all, how can I reconfigure it.
EDIT 3: So I think I found out a little more inside. I have a camera from FLIR, which uses a library called spinnaker. To install, one has to install a bunch of .deb packages. One of these is spinview_qt-.deb. It contains the QT5.7 version and installs to /usr/lib.
I think the problem may be that Ubuntu tries to find QT5 in /usr/bin before it looks in /usr/lib/x86_64-linux-gnu. So my question is, how can I achieve Ubuntu using the QT5.5.1 version as default again? Can I configure it or do I have to add the LD_LIBRARY_PATH always now? How can I uninstall the QT5.7 lib? Just delete the files listed above?
3.Temporary move Qt libraries supplied with camera package (/usr/lib/libQt*) to another location and check if spinview works fine with other version of qt than 5.7. If yes - you are free to delete qt5.7 libs from /usr/lib/ as they are not needed - no sophisticated uninstall process is necessary here. You can always restore it with your camera .deb package anyway.
Are you sure? In the requirements list on Zoom site I see libgstvideo which is part of gstreamer-plugins-base, although support article lists ancient version 0.10 while openSUSE comes with version 1.0.
The page on Zoom where I found the list is
-us/articles/201362003
There is a HELP tab (lower right). It opens to a list of top topics. The first entry when I found it was Installing or updating Zoom on Linux.
Scroll down to the list of dependencies specifically for openSuse:
EDIT:- New, re-written build now available. The mess of sym-linking 'gymnastics' is gone, and in its place is the use of the XDG protocol, which automatically keeps all config stuff within the portable's directory.....because Zoom-portable now thinks its directory IS the user's $HOME directory. Much neater, tidier, and far simpler to work with!
PLEASE NOTE:- When it comes to update time, run the supplied updater script. DON'T use the app's built-in one, 'cos it'll all go to hell in a handbasket... This can be run from the Menu entry under 'Network', if you've added these via the 'Menu-Add' script. If you're running it purely AS a 'portable', just click on the 'updt' script in the main directory.....and make sure you've fully closed Zoom from the tray icon before doing so.
Download has now been re-located to MediaFire; see link below.
Y'all must be getting fed-up with the seemingly never-ending procession of apps I keep giving the 'portable' treatment to! Here's another one I've been working on for a while, trying to figure out the best way to accomplish it. mow9902 gave me the idea a week or two back, when he discovered the AppImage builds for this, though I find the .deb download from their site seems to function better, and is easier to work with.
Once again, it's amenable to this kind of "treatment", because it's all contained within a single directory anyway. Unlike the 'portable-browsers', and Electron-based apps like Skype, which are built around a stripped-back Chromium browser, this is a completely unique, one-off build system....but the 'portable' treatment still works. And I'm of the firm opinion that 'portables' just fit so well with the Puppy 'ethos', and 'raison d'tre'...especially given the way so many of us run multiple Puppies.
I've built it along the same lines as the recent 'Skype-portable' I put together the other day. The config stuff all lives within a dedicated sub-directory inside the main 'zoom' one, and is then temporarily linked across to where they would normally be created, and 'looked-for' - the 'user' directory, which for us is /root with Zoom.
Unlike the 'Skype-portable', however (which uses a separate, 'transfer' script), I've figured out how to make use of, and transfer, existing Zoom config files with the launch script. When you run the portable for the first time, it copies across your existing config files, followed by deleting the originals.....necessary for the final step before launching, which is to sym-link them temporarily back to where Zoom thinks they actually are, in /root (because a sym-link will never be able to take precedence over an actual file). Upon closing Zoom, the sym-links are then deleted, meaning everything is back within the portable directory, which is where we want them!
If you've never used Zoom before, and the 'portable' is your first experience of it, the files are created as usual in their normal locations. At shut-down, they're copied over and the originals deleted, ready for the sym-linking trick next time you run it.....
Very nice! I've been using a version @step made for Fatdog mid last year. It still ran OK, but had been thinking for security it may be best to update to a current version. Problem solved. This portable version is excellent. Great job with the config file manipulation, it works a treat. Thank you.
Ah, I'm pleased to hear it works OK for you. It was a bit of a 'nail-biter', this one; I've tried out more than one new thing at a time. and despite trying it in every combination of existing config files (or not) and save-file/folder (or not), I was still a little unsure about it. Just because it worked for me was no guarantee it would for anyone else.
One or two of the file-manipulation routines are a wee bit 'redundant'.....by which I mean that they still run regardless of whether the files actually exist or not. Doesn't seem to affect script functionality, though. I've been experimenting with the conditional "if....then....else" stuff, but I don't think I've QUITE got the hang of it yet..!
Glad I tried this in Fossapup64 first. Today I tried to run it in BusterPup64 and couldn't get it to run. I then tried it with SCPup64 and Slacko64 7.0. The first attempts complain about the copying, so I then manually copied the config stuff to /root & /root/.config and still wouldn't run. Running in a terminal (after manually creating the config stuff) didn't even return an error to see what was going on, just returned to the prompt. The 3 manually created config files were deleted, so it appears to start, then exits doing the clean up at the end. I also tried 2 DebianDogs(BusterDog64 and SidDog) and had the same issues.
On FossaPup64 and Fatdog64 I had a bit of a play and it will also run as spot, but as you will know, the configs aren't deleted at the end. So, it will create the configs when run as spot on these 2 pup/fatdog. I may edit the scripts to run as spot.
Heh. Oh, I'll be the first to admit, this was a far bigger pain in the ass to get working in portable format than Skype was. That, by comparison, was easy compared to this.....which, in a way, is a tribute to M$ who, for a change, have gone the right route and 'standardised' around the default Electron set-up. And that makes it really easy to work with.....not least because I have some small amount of experience with the thing.
No, I may withdraw this, I think. It's not really running as well as I'd hoped it would. Can't have success with everything, can we..? (*shrug*) To me, this is one 'app' that actually works better as one OS, one install. It doesn't like being 'shared'..!
Thanks Mike! This is going to improve the quality of my life. I love the portable app approach. Ungoogled Chromium is by far the fastest Browser yet, I haven't figured out how to use sandbox so I can't download from it. But it's still great!
I may as well mention here, more for Terry's benefit than mine or yours, that Zoom is in some respects like Skype. Prior to standardising on a re-built .pet package format (followed by SFS, and now 'portable' - which works really well), I often found that the Skype .debs would 'install', but then wouldn't run.....and starting from the terminal shows absolutely no clue. Error messages have been deliberately suppressed, I guess; which is annoying, 'cos it doesn't even give you a chance to try and 'fix' stuff..!
Like I said, I'm going to withdraw this, until such time as I can get the problems ironed-out. For now, I'm going to recommend that Puppians install this as a proper install from the .deb package, here:-
(Please bear in mind that this really only runs successfully as a 64-bit app. To date, I don't know of anybody here that has had any success using the 32-bit version, despite that a 32-bit version is offered.)
I'm still hoping to be able to offer this as a 'portable', but not till I get the profile/config stuff 'sorted'. It may not be possible; many apps seem ideal for 'portable' treatment, since they're self-contained within a single directory.....but unless you can persuade them to write their profile/config stuff TO the 'portable' directory, you're whistling in the dark.
I installed the pet and it got zoom running, however its one step forward and then crash. My account logged in OK as it's in the profile. I then checked settings, video working OK. Then clicked test sound, zoom freezes and process has to be killed. Tried several times, same result.
As you went to the trouble of making the pet, it was worth trying. Thanks for your effort in helping to get this working, I hope others using ScPup64 can use it successfully. I have several installs I can use zoom on, so I'll use zoom with them when required.
c80f0f1006