So I just migrated a working application from Qt 6.1.2 to Qt 6.4.2. Pressed play in QtCreator and everthing ran, particularly the connection to a remote server which is done via HTTPS. I use QSslSocket::supportsSsl() to check that everything is ok with SSL and if it's not I close the application. So the fact the application opens means that everything is where it is.
I do however get this in the QtCreator console:
qt.tlsbackend.ossl: Failed to load libssl/libcrypto.
However it does work fine. I have tested.
Once I have this working I run windeployqt by doing
PATH/TO/windeployqt --qmldir PATH/TO/qmldir PATH/TO/myapp.exe
It runs and no errors. But now the application won't run neither from QtCreator (pressing play) nor from double clicking the executable. QtCreator console now throws THIS error:
qt.network.ssl: No functional TLS backend
I made sure that the libcrypto and libssl libraries (the same one in the OpenSSL directory installed by Qt Maintainer and in the bin directory of QtCreator) are in the executable's directory.
But I have no Idea why it is not working anymore. This exact same process worked on Qt 6.1.2 with no issues.
Any ideas?
EDIT: UPDATE: So I've been fooling around. And I found the following interesting tidbit. If I delete the QtCore6.dll from the executable directory where I ran the windeployqt, then I can launch the application from QtCreator again. I don't know if this helps anyone help me, but I'm putting it here just in case.
This question has been asked before, but the fixes don't work for me. I am running Windows 10 with WSL (Debian) and I am unable to run a QT program because of the error
texconv: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
I found a post which discusses the same problem. I've tried tolos' and Envek's solutions, but they don't work for me. For me the file is under /usr/lib/x86_64-linux-gnu/ like tolos' was. I also sudo-ed the strip and recompiled the qt program (If that even matters), but it still doesn't work.
If it matters, my kernel version (checked with uname -r) is 4.4.0-18362-Microsoft and I have no issues running this qt program on my other PC that uses WSL Ubuntu. And I installed the qt stuff with this command: sudo apt-get install qt5-default qtbase5-dev
I had an image that I would run using docker run and which would successfully launch KStars -- an application that uses this libQt5core.so.5.
If I ran the very same image on a Kubernetes cluster then I would get an error message when launching KStars like libQt5Core.so.5: cannot open shared object file: No such file or directory or some such.
Putting this strip command into the Dockerfile and rebuilding the image allowed the application to load successfully in both environments.
sudo strip --remove-section=.note.ABI-tag /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
I got it working in the end. I upgraded from WSLv1 to WSLv2 and that solved it. Not sure why, but it must have been a WSLv1 Debian bug
I am following the installation guidelines as described on mean.js.org Everything seemed to install fine. I have all prereqs installed. I ran npm install after cloning the github repo and then tried to run grunt and I didnt get any errors however It seems to just be stalling on the command line. Last message on the command line is the "debugger is running on port 5858" and then it just sits there.
After some time the message [nodemon] watching 51,839 files - this might cause high cpu usage. To reduce use "--watch" comes up. I am on windows 10 and have all the latest versions of node,npm,grunt and mean.js. I am running the command line as admin.
Mean.js should be running on localhost:3000 but it is not.
This is intended.
There is an application invoked by the grunt command and running in background, watching your files for changes. In default configuration: nodemon and grunt-watch.
This will execute specific tasks based on the files you edited, such as linting JS files or compiling LESS files.
The cmd will probably show something when you edit files in the projects directory.
I am running a GUI program in Qt and whenever I exit the program the error message in the Qt Creator terminal is
"The program has unexpectedly finished. /.../../.. exited with code 0".
However when I run this same executable through the Linux terminal and exit the program I get a segfault(core dumped) and consequently a core file. I was wondering if it is possible to enable the creation of core files by running the program from Qt Creator (not in debug mode, just build and run mode)?
Creating core files depends on the operating system rather than a single program or some IDE.
Try running
ulimit -c unlimited
on the shell before running qtcreator. Then you can try launch your program.
If you need more details take a look at the man page of bash.
Good luck!
Help!
I've been working with Meteor for about two months now, and everything is going swimmingly in my OSX home environment. But I recently brought some of that code into our Windows 7 environment at work, and Meteor isn't behaving the same on Windows.
Specifically, code bundling keeps getting borked. When I make changes to the code base, instead of flushing the old .meteor/local directory, and rebundling the application, it's barfing a ENOTEMPTY exception at me in the server console. If I halt the mongod process in Task Explorer and manually delete the .meteor/local directory, I can restart the application, and it will bundle and deploy the app with the new code changes.
Running on: http://localhost:3000/
No dependency info in bundle. Filesystem monitoring disabled.
Errors prevented startup:
Exception while bundling application:
Error: ENOTEMPTY, directory not empty 'c:\Users\Abigail\My Documents\GitHub\canvas tracker\.meteor\local\build\server'
at Object.fs.rmdirSync (fs.js:456:18)
at Object.module.exports.rm_recursive (c:\Program Files (x86)\Meteor\app\lib\files.js:256:10)
at c:\Program Files (x86)\Meteor\app\lib\files.js:254:15
at Array.forEach (native)
at Function._.each._.forEach (c:\Program Files (x86)\Meteor\lib\node_modules\underscore\underscore.js:79:11)
at Object.module.exports.rm_recursive (c:\Program Files (x86)\Meteor\app\lib\files.js:252:9)
at _.extend.write_to_directory (c:\Program Files (x86)\Meteor\app\lib\bundler.js:493:11)
at Object.exports.bundle (c:\Program Files (x86)\Meteor\app\lib\bundler.js:685:12)
at exports.run.restart_server (c:\Program Files (x86)\Meteor\app\meteor\run.js:615:26)
at c:\Program Files (x86)\Meteor\app\meteor\run.js:726:9
Please fix the problem and restart.
But it doesn't do on-the-fly code changes and re-bundles anymore. :( I'm also getting EPERM errors sometimes when I try launching the application.
Running on: http://localhost:3000/
No dependency info in bundle. Filesystem monitoring disabled.
Errors prevented startup:
Exception while bundling application:
Error: EPERM, operation not permitted 'c:\Users\Abigail\My Documents\GitHub\canvas-tracker\.meteor\local\.build.build'
at Object.fs.renameSync (fs.js:439:18)
at _.extend.write_to_directory (c:\Program Files (x86)\Meteor\app\lib\bundler.js:628:8)
at Object.exports.bundle (c:\Program Files (x86)\Meteor\app\lib\bundler.js:685:12)
at exports.run.restart_server (c:\Program Files (x86)\Meteor\app\meteor\run.js:615:26)
at c:\Program Files (x86)\Meteor\app\meteor\run.js:726:9
at Object.exports.launch_mongo (c:\Program Files (x86)\Meteor\app\lib\mongo_runner.js:146:5)
at exports.run.launch (c:\Program Files (x86)\Meteor\app\meteor\run.js:712:39)
at Server.exports.run (c:\Program Files (x86)\Meteor\app\meteor\run.js:770:5)
at Server.g (events.js:193:14)
at Server.EventEmitter.emit (events.js:90:17)
Please fix the problem and restart.
Any ideas on how to resolve this? I'm using Meteor 0.5.4 on Windows 7 Ultimate, SP1, x64.
Edit: I should mention that these errors occur whenever there's an error in the code. In my OSX environment, if I have an error, the code will still compile, minify, and bundle, and the page might not render and I'll get various Javascript errors in the Chrome console which I then have to debug. In my Win7 environment, I'm doing the exact same thing, but instead of compiling a semi-broken app that I can then debug in Chrome, it's halting during the bundle process. In either case, there's an error in my Javascript code (I know that much). But in OSX, it will still bundle and I can proceed to debugging. In Win7, I can't get to the debugging step because of these ENOTEMPTY and EPERM exceptions...
Edit: And, yes, I've tried nuking the permissions on the entire project directory by giving Full Access to Everyone. That didn't do the trick, unfortunately.
Win7. Two Steps to made it work.
1) Delete the DB Lock From MongoDB
C:\Users**USERNAME**\leaderboard.meteor\local\db
mongod.lock
2) Close all Open Editors pointing to files in project
C:\Users**USERNAME**\leaderboard.meteor\local\build\programs\client\app
leaderboard.js
In my case i kept an editor open to edit the leaderboard.js
It needs to be shut down, as the open file handle seems to interrupt.
Okay, so with the help of Tom Wijsman, we managed to track down the issue. The short answer is that it was the GitHub Bash shell.
The long answer is that ENOTEMPTY and EPERM are caused by a directory not getting deleted correctly during the bundling process. The directory not getting deleted correctly was caused by the code using an exec() command, which passed the delete command off to a shell. Turned out I was using the GitHub Bash shell, which is case sensitive, unlike the standard Windows cmd.exe, which is case insensitive. The case sensitivity was causing the shell not to recognize the path that should be removed, thus not removing it, thus causing a break during the bundle process.
100x thanks to Rahul for finding the previous bug reports on this issue! You were the hero that found the needle in the haystack!
Had the exact problem in windows 8. Turning off my McAfee antivirus (Real time scanning) just while running meteor cmd solved it.