Jump to content

Question

Posted

When starting Mo (version 1.3.8) I got following warning in the window at bottom where the "starting protokoll" is listed:

08:54:27 [W] QSslSocket: cannot resolve TLSv1_2_client_method
08:54:27 [W] QSslSocket: cannot resolve TLSv1_1_server_method
08:54:27 [W] QSslSocket: cannot resolve TLSv1_2_server_method
08:54:27 [W] QSslSocket: cannot resolve SSL_select_next_proto
08:54:27 [W] QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb
08:54:27 [W] QSslSocket: cannot resolve SSL_get0_next_proto_negotiated


08:54:50 [D] localization file qt_de-DE not found
08:54:50 [D] localization file organizer_de-DE not found

08:54:50 [D] localization file bsaExtractor_de-DE not found

08:54:50 [D] localization file gameSkyrim_de-DE not found
08:54:50 [D] localization file iniEditor_de-DE not found
08:54:50 [D] localization file installerBAIN_de-DE not found
08:54:50 [D] localization file installerBundle_de-DE not found
08:54:50 [D] localization file installerFomod_de-DE not found
08:54:50 [D] localization file installerManual_de-DE not found
08:54:50 [D] localization file installerNCC_de-DE not found
08:54:50 [D] localization file installerQuick_de-DE not found
08:54:50 [D] localization file NMMImport_de-DE not found
08:54:50 [D] localization file previewBase_de-DE not found
08:54:50 [D] localization file proxyPython_de-DE not found

08:57:57 [W] QIODevice::read: device not open
 

I didn´t recognized any issues yet. But as a beginner I´m little unconfident.

Is this a warning I could ignore?

Or is there some troubleshooting to do?
i the last case I like to know, what I should do.[]

5 answers to this question

Recommended Posts

  • 0
Posted

With the 'Sort' tool (a stripped down version of LOOT) in the 1.3.x versions, there is no report window after sorting your plugins. If you need the report afterward you can install and run the full LOOT from inside MO.

  • 0
Posted

These messages:
 

08:54:27 [W] QSslSocket: cannot resolve TLSv1_2_client_method
08:54:27 [W] QSslSocket: cannot resolve TLSv1_1_server_method
08:54:27 [W] QSslSocket: cannot resolve TLSv1_2_server_method
08:54:27 [W] QSslSocket: cannot resolve SSL_select_next_proto
08:54:27 [W] QSslSocket: cannot resolve SSL_CTX_set_next_proto_select_cb
08:54:27 [W] QSslSocket: cannot resolve SSL_get0_next_proto_negotiated

 

are nothing to worry about. QT5 is complaining that windows 8 doesn't support old versions of SSL. Presumably at some point QT5 will stop checking, as no one should be using those (compromised) versions anyway

These
 

08:54:50 [D] localization file qt_de-DE not found
08:54:50 [D] localization file organizer_de-DE not found
08:54:50 [D] localization file bsaExtractor_de-DE not found
08:54:50 [D] localization file gameSkyrim_de-DE not found
08:54:50 [D] localization file iniEditor_de-DE not found
08:54:50 [D] localization file installerBAIN_de-DE not found
08:54:50 [D] localization file installerBundle_de-DE not found
08:54:50 [D] localization file installerFomod_de-DE not found
08:54:50 [D] localization file installerManual_de-DE not found
08:54:50 [D] localization file installerNCC_de-DE not found
08:54:50 [D] localization file installerQuick_de-DE not found
08:54:50 [D] localization file NMMImport_de-DE not found
08:54:50 [D] localization file previewBase_de-DE not found
08:54:50 [D] localization file proxyPython_de-DE not found

 

imply that your install wasn't done correctly and the German translations of various messages and files aren't available. It's nothing to worry about, except a lot of tool tips and help pages will be in English

This one
 

08:57:57 [W] QIODevice::read: device not open

 

I have never seen before. I imagine of mod organiser is running OK, it's not really a problem. However, it may be  another issue with the install. Try downloading the full install and reinstalling.

  • 0
Posted (edited)

Thank You Thosrtanner

 

the fresh install solved it not really:  "[W] QIODevice::read: device not open"   is not shown at the beginning.

But with running implemented Loot to sort plugins espacially with the unofficial patches the message shows again.

 

Edit: Now I have little idea what this message mean. After running the implemented Loot you got usualy a report in an extra window.

I got no report, though Loot seems to work properly. Reinstalling with a new download didn´t fix it.

Edited by Imrazon
  • 0
Posted

I have the same issue, I consider myself pretty expierenced, a Gopher type (the scottsish version), I have narrowed this down to MO, Mo has a problem, i used the same mods with NM, no crash problem...hmm

 

Jim

  • 0
Posted

Welcome to STEP @JimmySmith

 

Perhaps you should post a fresh topic about your experience as this one wasn't about a 'crash', simply some messages that recur.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.