Hmmm, there's got to be more to it than this. Works fine everywhere else. Something unique about your system that would cause it to need to access your drive by using that particular path?
No, this is a normal installation on my hdd. I have the sourcecode as well so I'll build a version myself. I hope this is not some kind of hw failure, though probably you hope it is :-)
Ok, I think I found the issue: it seem MuseScore is scanning the available drives - and if there is a drive which is reported existing but not available it will not start.
So steps to reproduce:
- take a Huawei E1752 3G Modem or similar stuff which has an optional SD-card port
-- this modem will display 2 extra drives, one CD (containing the driver software) and one removable disk (not available, as I don't have the SD card inserted)
- start mscore - mscore will report that it cannot start
I think this can be an error with other configurations (virtual disks etc.)
For me this is indeed critical as I cannot use MuseScore online via mobile net.
My desktop has 4 optional drive letters from my USB cardreader and a CD-ROM without a disk in it. I also have an average of 6 network drives mapped, sometimes they aren't available. No issues from any of them. The launch drive is D for my custom build, the other ones are higher (F-J, M and up).
I started a git bisect, but meanwhile this log looks quite relevant, as my removable drive is drive G
Auto configuration failed
2624:error:02001015:system library:fopen:Is a directory:.\crypto\bio\bss_file.c:126:fopen('g:/phpbuild/apps_install/openssl.
cnf','rb')
2624:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c:131:
2624:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\conf\conf_def.c:199:
Warning: QMutex: destroying locked mutex (thread\qmutex.cpp:201, QMutex::~QMutex())
The previous commit also has the issue, but only appears when I press "Start" in the MuseScore Connect widget.
2 interesting things:
- running with QT Creator Debug the error doesn't happen
- if I set the PATH environment variable to empty, the error doesn't happen
So it is probably related to reading a bad openssl dll from the path.
In QT Creator Debug it uses a QT/Tools ssleay32.dll, when running in normal mode, it takes one from the path (my XAMPP server), where OPENSSLDIR is set as g:/phpbuild/apps_install/ in libeay32.dll.
If these dlls are not on the path at all it seems MuseScore (or Qt5Network) doesn't load them at all (checked with ListDlls), so it probably uses some statically linked ssl, while if there is something on the path, it will use dll.
For me I did the following workaround: copied the OpenSsl DLLs from QT to C:\Windows
Comments
Hmmm, there's got to be more to it than this. Works fine everywhere else. Something unique about your system that would cause it to need to access your drive by using that particular path?
Did you install MuseScore on a network share?
No, this is a normal installation on my hdd. I have the sourcecode as well so I'll build a version myself. I hope this is not some kind of hw failure, though probably you hope it is :-)
Ok, I think I found the issue: it seem MuseScore is scanning the available drives - and if there is a drive which is reported existing but not available it will not start.
So steps to reproduce:
- take a Huawei E1752 3G Modem or similar stuff which has an optional SD-card port
-- this modem will display 2 extra drives, one CD (containing the driver software) and one removable disk (not available, as I don't have the SD card inserted)
- start mscore - mscore will report that it cannot start
I think this can be an error with other configurations (virtual disks etc.)
For me this is indeed critical as I cannot use MuseScore online via mobile net.
My desktop has 4 optional drive letters from my USB cardreader and a CD-ROM without a disk in it. I also have an average of 6 network drives mapped, sometimes they aren't available. No issues from any of them. The launch drive is D for my custom build, the other ones are higher (F-J, M and up).
I also have CD-reader without disk, so it's indeed not so simple, but when I remove the modem MuseScore starts up well.
I started a git bisect, but meanwhile this log looks quite relevant, as my removable drive is drive G
Auto configuration failed
2624:error:02001015:system library:fopen:Is a directory:.\crypto\bio\bss_file.c:126:fopen('g:/phpbuild/apps_install/openssl.
cnf','rb')
2624:error:2006D002:BIO routines:BIO_new_file:system lib:.\crypto\bio\bss_file.c:131:
2624:error:0E078002:configuration file routines:DEF_LOAD:system lib:.\crypto\conf\conf_def.c:199:
Warning: QMutex: destroying locked mutex (thread\qmutex.cpp:201, QMutex::~QMutex())
According to git bisect the first bad commit is:
5558e9f
Based on the log it might be related to qt network manager and ssl,
The previous commit also has the issue, but only appears when I press "Start" in the MuseScore Connect widget.
2 interesting things:
- running with QT Creator Debug the error doesn't happen
- if I set the PATH environment variable to empty, the error doesn't happen
So it is probably related to reading a bad openssl dll from the path.
In QT Creator Debug it uses a QT/Tools ssleay32.dll, when running in normal mode, it takes one from the path (my XAMPP server), where OPENSSLDIR is set as g:/phpbuild/apps_install/ in libeay32.dll.
If these dlls are not on the path at all it seems MuseScore (or Qt5Network) doesn't load them at all (checked with ListDlls), so it probably uses some statically linked ssl, while if there is something on the path, it will use dll.
For me I did the following workaround: copied the OpenSsl DLLs from QT to C:\Windows
Hi Bertalan Fodor, are you still having problems?
This can be closed, but good to know for reference, that having some ssleay32.dll and/or libeay32.dll on path might cause problems.